Fritz: All Fritz

home *** CD-ROM | disk | FTP | other *** search

/ Fritz: All Fritz / All Fritz.zip / All Fritz / FILES / COMMADIO / PK232COM.LZH / PK232COM.DOC < prev next >

Wrap

Text File | 1988-01-29 | 192KB | 4,159 lines

PK232COM VERSION 1.48 PAGE 1 PK232COM Version 1.48 (c) 1988 by G3ZCZ (C) Copyright 1987 - All Rights Reserved By Joe Kasser G3ZCZ POB 3419, Silver Spring, Md., 20901, USA. A Personal Packet Terminal Program for the TNC1, TNC2, KPC-2 and most of all a smart multi mode digital communications controller for the PK-232. PK232COM is written and supported by Joe Kasser, G3ZCZ. The program is distributed as a Shareware product. You may freely copy and share the product for non commercial use, with your friends, associates and other radio hams. If you decide to use the product, you are asked to become a registered user by sending a QSL card and a contribution to the author (suggested amount of $35.00 or equivalent in foreign currency. The contribution covers the cost of distribution of the updated disk, and supports the continual development of "Software for Amateur Radio". Upon receipt of your contribution, you will receive AT LEAST one free update disk CUSTOMIZED with YOUR CALL- SIGN (if you write the type of TNC on the QSL card.), mail (electronic and regular) support, and notice of further releases. This product may not be sold or distributed with another product without the express written permission of Joe Kasser, G3ZCZ. Joe Kasser, G3ZCZ will only support unmodified copies of this software. Your comments and suggestions for changes are however welcome. If you are the first to suggest a change that is imple- mented, you will be sent a complimentary copy of the disk with the change incorporated. Potential Commercial Users please contact Joe Kasser directly for details of Site licensing. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 2 CONTENTS ------------- 1.0 INTRODUCTION 1.1 PROGRAM HIGHLIGHTS 1.1.1 MORSE/BAUDOT/AMTOR/ASCII 1.1.2 PACKET RADIO 2.0 CRT DISPLAY 2.1 Status Display 2.2 Incoming Text Display 2.3 Outgoing Text Display 2.4 Alarm Tones. 3.0 Function keys. 3.1 Function Keys 3.1.1 Capture to Disk Toggle 3.1.2 Transmit a file 3.1.3 CAllsign Sequence. 3.1.4 Brag tape 3.1.5 Call CQ 3.1.6 Change Communications Modes 3.1.7 Call/Connect 3.1.8 Disconnect or Receive 3.1.9 Command Mode 3.1.10 Transmit Mode 3.2 Alt Function keys 3.2.1 Exit or return to DOS. 3.2.2 Initialize the PK-232. 3.2.3 Connect Status 3.2.4 Set Terminal Mode 3.2.4.1 SOLO 3.2.4.2 TRAFFIC 3.2.4.3 CQ/BEACON 3.2.4.4 READ THE MAIL 3.2.4.5 Multiple Connect Modes. 3.2.4.5.1 The Individual Multi Connect Mode. 3.2.4.5.2 The Conference Multi Connect Mode. 3.2.4.5.3 The Bridge Multi Connect Mode. 3.2.4.5.4 Entering the confer- ence mode 3.2.4.5.5 Connecting in the multi user mode 3.2.4.6 FEC 3.2.4.7 ALISTEN 3.2.4.8 ACHG 3.2.4.9 ARQ 3.2.4.10 Force LETTERS Case 3.2.4.11 Override Mailbox/Beacon. 3.2.4.12 Turn on Mailbox/Beacon. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 3 3.2.5 Monitor Channel Activity 3.2.6 Change Packet Connect / Contest / CQ text Message 3.2.6.1 Change Packet Connect Message 3.2.6.2 Change Contest Message 3.2.6.3 Change CQ text Message 3.2.7 Enter Call Sign 3.2.8 Not used. 3.2.9 Activate Transmit Buffer 3.2.10 Help 3.3 Shift Function Keys 3.3.1 Dir 3.3.2 Rename 3.3.3 List of Outgoing Messages to be sent. 3.3.4 Delete 3.3.5 List of messages that have been sent. 3.3.6 Mail Beacon Activate 3.3.7 Retry a call/connect request 3.3.8 Not used. 3.3.9 Connected Indicator Reset. 3.3.10 OVER function. 3.4 Control Function Keys 3.4.1 Day Flag 3.4.2 CWID 3.4.3 Message Uploading 3.4.3.1 Leaving a Note in your system. 3.4.3.2 Leaving a message on an other PK232COM system [QSP]. 3.4.3.3 Uploading messages to another PK232COM system. 3.4.4 Show last few log entries. 3.4.5 Automatic CQ Sender 3.4.6 SELCAL 3.4.7 Beacon Activate Toggle/CQ Wait Delay Adjust. 3.4.7.1 Beacon Mode Toggle/On-Off 3.4.7.2 CQ Delay Time Adjust 3.4.8 Not used. 3.4.9 Transmit Buffer Clear 3.4.10 Log QSO 3.5 Shift/Baudrate Control keys 3.5.1 The RIGHT ARROW Key (Increase Baudrate). 3.5.2 The LEFT ARROW Key (Decrease Baudrate). 3.5.3 The UP ARROW Key (Change shift). 3.5.4 The DELETE Key (toggle USOS). 3.6 Additional keys 3.6.1 The HOME Key. 3.6.2 The DOWN ARROW key. 3.6.3 The Alt A key (Alert Call Set/Toggle). 3.6.4 The Alt B key (BAUDOT/ASCII baud Rate Set Key). PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 4 3.6.5 The Alt C key (Connect/Call). 3.6.6 The Alt D key (Disconnect). 3.6.7 The Alt F key (Digipeat Monitor Set/Toggle). 3.6.8 The Alt M key (Mail scan). 3.6.9 The Alt P key (Printer Toggle). 3.6.10 The Alt R key (Message Relay toggle). 3.6.11 The Alt S key (Sound Set/Toggle). 3.6.12 The Alt T key (Target Call Set/Toggle). 3.6.13 The Alt X key (Exit or return to DOS). 3.6.14 The Alt Z key (Initiates a BBS mail dump). 3.6.15 The PgUp key (Scrolls back Incoming). 3.6.16 The Control Z key (AMTOR +?). 4.0 PK232COM disk files 4.1 PK232COM.COM 4.2 PK232COM.RUN 4.3 PK232COM.SYS 4.3.1 The callsign. 4.3.2 The AMTOR SELCAL. 4.3.3 The CQ Text. 4.3.4 The fourth and fifth lines (Band and Power). 4.3.5 The CQ Delay time. 4.3.6 The Message Relay Capability (QSP). 4.3.7 The Communications Port. 4.3.8 The TNC type. 4.3.9 The Terminal Baud Rate. 4.3.10 The QTC_Snatch flag. 4.3.11 The BBS_MAIL_Snatch flag. 4.3.12 The Remaining lines. 4.4 PK232COM.LOG 4.5 PK232COM.DIR 4.6 CONFIG.SYS 4.7 *.MBX 4.8 *.BBS 5.0 Initialization 6.0 Running the Program 7.0 Mailbox Features (AMTOR/Packet Modes Only) 7.1 Answering Machine. 7.2 Mail Beacon (Annunciator). 7.3 How to leave a message 7.4 Remote File Downloading (Packet Mode Only). 7.5 Remote Beacon shutdown. APPENDIX 0. UPDATES/REVISION HISTORY. APPENDIX 1. BUGS and Anomalies. A1.1 Command/Converse mode anomalies. A1.2 Buffer messages in AMTOR Beacon CQ mode. A1.3 FEC +? responses in AMTOR Beacon CQ mode. A1.4 PK232COM versions 1.00 to 1.39. A1.5 Using a CGA card with a monochrome monitor. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 5 A1.6 The Packet Conference Mode. A1.7 Packet Conference Mode disconnects. A1.8 Slow Screen Updating. A1.9 Strange Events. A1.10 *** DISCONNECTED. A1.11 Greek Characters on Incoming Screen. APPENDIX 2. MESSAGES IN A LOCAL AREA NETWORK A2.1 LAN Protocol (G3ZCZ Version). A2.2 Message Format. A2.3 File Uploading/Downloading. A2.4 Path Determination to a Dx station. APPENDIX 3 BASIC NC/L DICTIONARY A3.1 :QBM: To Download a file. A3.2 :QDB: To Upload a file. A3.3 :QMH: To request a call monitored list ('MH'). A3.4 :QSM: To request a repeat of a message. A3.5 :QSP: To leave a message for another station. A3.6 :QRT: To shut down a packet beacon station. A3.7 :QRU: To upload messages. A3.8 :QNO: Error or function not present/active. A3.9 :QJG: No more messages pending. A3.10 :QRV: Ready for message. A3.11 :QSL: Confirm receipt of message. A3.12 :QTC: Message list. A3.13 :QYU: YAPP format file upload. A3.14 :QYD: YAPP format file download. APPENDIX 4. USING OTHER TNC'S. 4.1 TNC2 (MFJ 1270) A4.1.1 Default Commands. A4.1.2 Program differences. 4.2 TNC1 (HD-4040) A4.2.1 Default Commands. A4.2.2 Program differences. 4.3 Kaypro KPC-2 A4.3.1 Default Commands. A4.3.2 Program differences. APPENDIX 5. NOTES and ACKNOWLEDGEMENTS. APPENDIX 6. REGISTRATION FORM. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 6 1.0 INTRODUCTION PK232COM is a Personal Digital Communications Terminal Program for a Packet Radio TNC. While it takes advantage of the extra features of the PK-232 which is made by Advanced Electronics Applications Inc. MANY OF THE PACKET RADIO FEATURES WILL WORK ON A TNC1 AND MOST OF THESE FEATURES SHOULD WORK ON ANY TNC2. It is designed to allow anyone to use and get the most out of the PK-232 for Morse, ASCII, BAUDOT, AMTOR as well as Packet Radio communications without having to keep the PK-232 or other TNC2 manual handy. PK232COM is a sophisticated program. In its basic state it allows you to use the TNC in an optimal manner. It configures the TNC for you to maximize the communications efficiency in the communications mode of your choice. That means, for example, when working Packet on HF you need to program the TNC parameters to different values than you would use on VHF to make maximum use of the mode. One significant difference is the length of the packet itself, for the longer it is, the greater the probability of QRM destroying it. This program will adjust the packet parameters for you. Since the computer is now involved, other features have been added to simplify operation, and several features have been automated. All these operations are performed using function keys as documen- ted below. It will take a while to learn how to use this program in a manner that suits you, read this document and have fun, after all, isn't that one of the purposes of Amateur Radio. This documentation file is not a manual. It is a preliminary document. It is written to remind you of what the program can do. If there is enough interest (registrations) I will expand it. It is not designed to explain the theory behind the different communications modes. Read the TNC Manual for more information. This program is designed to optimize the configuration of the TNC in each communications mode and to provide some smart terminal features. 1.1 PROGRAM HIGHLIGHTS Function key and Menu driven. 1.1.1 MORSE/BAUDOT/AMTOR/ASCII Automatic CQ caller. Will call CQ repetitively and signal you when a reply is received. RTTY SELCAL. Automatic capture to disk of all ingoing and outgoing text of any QSO. AMTOR/PACKET Selective answering machine and MAILBOX using NC/L command dialog. AMTOR function key change from monitoring FEC CQ's to QSO's in PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 7 progress (chirpcopy). 1.1.2 PACKET RADIO Automatic disk recording of all packet radio connects. Auto- matic indication of Packet connects. AMTOR/Packet Local Area Network (LAN) message store and forward. Capable of automatic connect attempts to download a QTC from an other station in the LAN. Capable of automatic connect attempts to a packet BBS to download your incoming messages, when your callsign appears on the BBS mail beacon annunciator. Digipeat monitoring and capture. Alert signal to let you know when a predetermined call shows up in a packet header on frequency. Conference mode in multi- connect situations. Bridge mode in multi- connect situations. Path determination to Dx station via :QMH:. Indicator that a specific station designated as the 'target' call connected in Packet mode, or linked to AMTOR Beacon/Mail- box while you were away. Automatic NET/ROM path set up from PK232COM.DIR call/path directory file. AMTOR/PACKET Automatic Answering Machine capability with display of message queue. Automatic Beacon Mode CQ caller in Packet and AMTOR communi- cations modes. Will call CQ repetitively and either work the connect and keep going after disconnect or signal you when a reply is received. Automatic logbook entries for Packet and Mailbox/Beacon mode AMTOR Connects, semi automatic logbook entries for other modes. Log file is compatible to that of the G3ZCZ CONTEST program can be processed by the DBASE Logbook Package of PC-HAM by G3ZCZ for indexed listings, tracking of DXCC and other AWARDS, etc. Contest operation, sends standard message and automatically increments QSO count. Automatic optimized configuration of the TNC for each com- PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 8 munications mode. Function key 'OVER' feature (Shifted Function key 10). Morse, ASCII, BAUDOT communication modes are HALF DUPLEX. One station is transmitting at any time. You thus have to use the Transmit/Converse and Receive/Disconnect function keys to turn the transmitter on and off respectively. AMTOR is also HALF DUPLEX but has some of the attributes of full duplex. In this mode you control who is talking through software, only one station can send data at a time, but you can type characters in to the buffer and they will be transmitted automatically when the other station turns the QSO over to you. Once you have linked with someone, you do not use the Receive/Disconnect function UNTIL THE QSO IS OVER. Both stations are communicating automatically thanks to the TNC. If you want the other operator to respond type the +? key sequence (or use shift function key 10). Packet Radio communications on the other hand is a full duplex mode of communications. Once you have connected with someone, you do not use the Receive/Disconnect function UNTIL THE QSO IS OVER. Both stations are communicating automatically thanks to the TNC. If you want the other operator to respond type the > key followed by the 'Enter' key, better yet, use shift function key 10. Note that Morse, AMTOR, ASCII and BAUDOT are character mode communications in that each character you type is sent as you type them. In Packet Communications, the TNC stores them up and sends out a burst or packet when you type the 'Enter' key or you type enough characters to fill up a packet. Studies have shown that the human attention span when sitting at the keyboard is of the order of 2 seconds. If you are in a keyboard to keyboard packet radio connect, remember this and don't forget to use the 'Enter' frequently especially before you stop to think about what to send next. Any Terminal Node Controller (TNC) is a complex piece of equipment. It can operate in a Command Mode, in which you tell it to do something, or in a Converse Mode in which you are using it to talk to other stations. Many people confuse the two when first getting on Packet. If you monitor the channels you will recognize command mode TNC instructions on the air, and when you use the TNC you will receive the "?error" reply when you type something thinking that you are in the Converse Mode but are really in the Command Mode. PK232COM is designed to make Packet operation simple using high level (Function key) commands. This Version has the following functions built in to it in a menu driven format. Morse Code 20 wpm (CW). BAUDOT with default of 45 WPM narrow shift (LSB). You may set PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 9 other baud rates directly, or use the left and right arrow keys to change the baud rate (see below). ASCII with default 110 BAUDS narrow shift (LSB). You may set other baud rates directly, or use the left and right arrow keys to change the baud rate (see below). Packet VHF or HF baud rates and shifts (LSB). AMTOR 100 BAUDS narrow shift (LSB). All communications between the computer and the TNC normally use COMM1 and operate in the 8 BIT NO PARITY and 1 stop bit RS-232 Serial Port configuration. You CAN SEND FOREIGN LANGUAGE CHARACTERS FROM THE KEYBOARD OR FILES. If you want to limit the character set to the 7 bit ASCII set, set the TNC parameters accordingly. The baud rate defaults to 1200, but you may set it to 2400, 4800 or even 9600 if your CPU clock is fast enough. Access to the TNC Command mode is provided in case the user wishes to override any of these defaults. IF YOU USE THIS PROGRAM, YOU STILL MUST READ THE TNC MANUAL. Note that AMTOR and PACKET are full duplex modes of communications. When you connect with someone, there is no need to use the transmit and receive function keys. In fact you will have problems if you do. Do not disconnect until the QSO is over. WARNING .... THIS PROGRAM OPERATES IN AN OPEN LOOP MODE. IT REMEMBERS WHAT INSTRUCTIONS OR COMMANDS IT GAVE THE TNC. IF FOR SOME REASON, THE TNC IS NOT SYNCHRONIZED TO THE PROGRAM YOU WILL NOT GET CORRECT DISPLAYS ON THE SCREEN. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 10 2.0 CRT DISPLAY The CRT display contains three areas as follows. ------------------------------------------------- | STATUS DISPLAY | ------------------------------------------------- | | | | | INCOMING TEXT DISPLAY | | | | | | | ------------------------------------------------- | OUTGOING TEXT DISPLAY | | | | | | | ------------------------------------------------- 2.1 Status Display A one line display at the top of the screen showing the status of the communications system. The left side of the screen normally displays the "capture to disk" or logging status, the center of the screen displays status information depending on which of the operational modes is active. 2.2 Incoming Text Display The center section of the screen displays data coming back from the TNC. This consists of data received via the radio communications link, TNC status information and transmitted data echoed back by the TNC. 2.3 Outgoing Text Display The lower area of the screen shows data being sent to the TNC. This consists of command data from the program to the TNC, text typed by the user and files being transmitted. 2.4 Alarm Tones. PK232COM sounds a different number of alarm tones or chimes according to the following events; 1 Digipeat Detected. File Alarm Error. 2 PK232COM :QTC: message detected, automatic QTC_Snatch connect request in progress. Tones toggled back on. 3 Alert Call heard in packet header. 5 Somebody connected. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 11 The alarm tones may be toggled ON/OFF by means of the Alternate S key. 3.0 Function keys. PK232COM can be used as a simple Terminal Interface Program with the 10 main function keys. The control, alternate and shift function keys provide advanced features. You should first become familiar with the function keys described in Section 3.1 and then expand your use of the program to incorporate the remaining expanded function keys. Don't try to learn them all at once. The operation of each of the function keys are explained below. 3.1 Function Keys 3.1.1 Capture to Disk Toggle This key toggles the "capture to disk" function. When the function is active, all incoming text (including 'Echo as sent' outgoing text) is stored on a disk (floppy or hard) in a file called 'PK232COM.RUN'. If this file does not exist the first time that PK232COM is loaded, it is created. From that time on, successive activations append new data to the contents of the file. Each time the function is activated a datestamp (or timetag) will be written to the file. When a Packet station connects the 'capture to disk' function will be activated automatically even if you have not set it active. Packet connects will thus be recorded in their entirety automatically unless you turn off the 'Capture to disk' during the course of the QSO. The function will be deactivated at disconnect time unless you have toggled it on. You may later edit the file at your convenience with your favorite word processor. PK232COM will automatically close the log capture file when you terminate the program and return to DOS. 3.1.2 Transmit a file This function allows you to transmit an ASCII file via the PK-232. You may abort the transmission sequence at any time by depressing any of the function keys, the keys on or associated with the numerical pad, or the ESC key. During the file transfer, the status window will PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 12 show the different states of the transmission. It begins with a signal that the message is being sent. If the text is long and fills the TNC buffer, you will see a message 'QRX TNC BUFFER FULL' possibly followed by 'TNC NOT RESPONDING'. This latter message will seem to blink periodically. When the TNC signals that it is ready to accept more text, the message sequence will resume. In the Packet Communications mode, when the file has been loaded into the TNC the computer will add the ^Z character to the outgoing text to signal to the recipient that the file transmission is over. The computer will signal you (using the bell character, when the file has been loaded into the TNC, Note that is not the same as the time that the TNC has transmitted the file, because the TNC incorporates a character buffer. 3.1.3 Call Sign Sequence. This function lets you transmit the following sequence <other call) DE <your call>. For example if you are 4X6AA and you are working G3ZCZ then this function would transmit the sequence G3ZCZ de 4X6AA. You use this at the start of a transmission in any mode except Packet. 3.1.4 Brag tape This function allows you to transmit a standard text file historically known as a "Brag Tape" via the TNC. The brag tape file must be called PK232COM.TXT, and should be created with a word processor in the non-document mode. Transmission of the Brag Tape may aborted in a similar manner to that of a regular file (see above). 3.1.5 Call CQ You use this function key to call CQ. In the Packet Communications mode, the TNC will transmit a line of text along with the CQ packet. The line of text is set up in the PK232COM.SYS file described in section 4. In the AMTOR communications mode, your SELCAL will be transmitted along with the CQ call in the FEC mode. 3.1.6 Change Communications Modes This function allows you to change the communications mode of the PK-232. Allowable modes PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 13 are Morse code, BAUDOT, AMTOR standby, AMTOR Alisten, ASCII, Packet and Signal. In the Packet mode you can choose VHF or HF operation in a single step by entering the letters V or H. When you select the AMTOR standby mode you are placed into the 'standby receive' mode. If you want to read the mail on an existing AMTOR QSO in progress, select the AMTOR Alisten or chirpcopy mode. If you are in AMTOR standby mode, you will not be able to see signals of the chirpcopy mode. Use the 'G' option to select the 'SIGNAL' mode. Read the PK-232 documentation carefully to understand how this mode works. Once the PK-232 has identified the digital signal it is tuned to, use the same function key a second time to select the relevant mode and set the baud rates and shift to display the data. 3.1.7 Call/Connect You use this function to call a station heard on the band, or to attempt a connect with another packet station. You may also use it to call 'QRZ' or even 'TEST'. In AMTOR the call will be sent in the ARQ mode to the SELCAL of the desired station. In the Packet Communications mode you can create a directory file and keep a list of names and callsigns. The computer will look up a name and call the station by its callsign. For example if you put Joe G3ZCZ as a line in the file, when you tell the computer to connect to Joe, it will try to connect to G3ZCZ. If you enter 4X4HF 4X4HF V 4X1AA 4Z4ZB 4X4IL you only need to type '4X4HF' to set up the correct connect path. See section 4.5 which describes the PK232COM.DIR file for further information. You can also use this function key to automate a NET/ROM path connection. In the manual NET/ROM path setting up mode, you would first connect to your local node, then when you are connected with it, connect to the next node, and so on through any intermediate nodes within the whole path before you finally connect with your destination station. You may have digipeaters in any of the paths. For example if you wish to connect to K1HTV who is in range of the SSCT node, and you are in Washington PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 14 DC, you would first have to connect to your local NET/ROM node (ELK), then the intermediate nodes, SNJ3, NNJ, WMA before you could try to connect with K1HTV. If you put the following line in the PK232COM.DIR file K1HTV ELK v WB4APR-5! SNJ3! NNJ! WMA! SCCT! K1HTV the NET/ROM sequence will be automatic. PK232COM will issue a 'disconnect' command to the TNC in the event the NET/ROM connect attempt fails. This function is designed for known paths not for general path determination. In the Packet communications mode, if you want to loop back through someone else enter the '/' character followed by the call of the station you want to loop back through. For example if I (G3ZCZ) want to loop back through 4X6AA, I just need to enter /4X6AA as the call to connect to and the computer will tell the TNC to try to connect to G3ZCZ via 4X6AA. In a multi connect situation the program will automatically select a free IO channel to try the connect on. 3.1.8 Disconnect or Receive This function key returns the station to the receive communications (TNC command) mode. It may also be used to abort the automatic CQ sequence. If you use it to abort a CQ sequence while the transmission is in progress, flush the PK-232 transmit buffer using Control function key 9. In a multi connect situation the program will prompt you to tell it which IO channel to disconnect. In AMTOR this function key toggles PK232COM between the Chirpcopy mode (listening to a QSO in progress) and monitoring FEC transmissions (CQ calls). 3.1.9 Command Mode This function puts the TNC into the command mode. At this time, the program is transparent and acts as a dumb terminal (except for placing incoming and outgoing text in the relevant windows). You use this mode for overriding any of the TNC default conditions. (SEE I TOLD YOU THAT YOU HAD TO READ PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 15 THE TNC MANUAL). 3.1.10 Transmit Mode This function places the TNC into the transmit or converse mode. The transmitter is turned on and the contents of the transmit buffer is transmitted. In the non packet communications modes, the outgoing characters will be echoed back from the TNC and displayed in the INCOMING window on the CRT as they are transmitted on the air. 3.2 Alt Function keys 3.2.1 Exit or return to DOS. Exits the program and returns you to DOS. When you exit the program, the TNC is put into the VHF default mode in which it rejects calls from any other stations. (Read about the 'CFROM' command in the TNC manual). you can thus if you wish leave it powered, and if you also leave the VHF radio powered up, you will be active as a digipeater, but at the same time anyone trying to connect with you will receive a busy signal. The MBX function (Reading the Mail) is also cleared at this time. 3.2.2 Initialize the TNC. Sets up the defaults for the TNC from the file PK232COM.SYS. If you have put batteries in the TNC, you should normally only have to run this function when you first power up the TNC or change the batteries. It will also set the date and time within the TNC from the computer clock, and, when it has loaded the configuration file, may prompt you to set the TNC Terminal mode. If you are using a TNC1 or a TNC2, it will not prompt you because it knows they only operate on VHF packet. If you are using a KPC-2, you may select 'H' or 'V', and of course, if you have a PK-232, you may chose any of the options. 3.2.3 Connect Status When you are in the Packet communications mode, this function lets you see the state of the connection in the Command Window. It will show you if there are any unacknowledged packets en route to the other station. If you have been sending text, it is advisable to use this function before you disconnect, just to ensure that all the data has been received and acknowledged by the other party. You may use this function in either the TNC Command PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 16 or the TNC Converse mode. If you use it when in the Converse mode, it will leave you in the command mode, so remember to use function key 10 to return to the converse mode. In a multi connect situation, it will show you the status on all the IO channels (It uses the 'C' TNC command in the single user mode and the 'CS' TNC command in a multi user situation). You may also use this function to reset the status window display after a relink or any other event which was not reflected in the status window. 3.2.4 Set Terminal Mode This key allows you to set the terminal configuration mode. In Packet communications many stations can use the channel at the same time. Refer to the "MONITOR' and 'MBX' commands in the TNC manual. These modes give you some degree of control as to how the packets from different stations are displayed on your screen. In the PACKET Communications mode, the function works in the following manner. You can set four Packet terminal modes as follows. 3.2.4.1 SOLO In this mode, you will only see messages addressed to you. You will only get messages from people who connect to you. (This corresponds to 'MONITOR 0'). 3.2.4.2 TRAFFIC In this mode you will see most of the traffic on channel. you can use this mode to check that the TNC is working. (This corresponds to 'MONITOR 4' or 'MONITOR ON'). You can also set the TRAFFIC mode to 'Everything' if you have a PK232 which corresponds to 'MONITOR 6'. 3.2.4.3 CQ/BEACON In This mode, you will see CQ and BEACON packets on the channel. (This corresponds to 'MONITOR 1'). This mode only works on the PK- 232. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 17 3.2.4.4 READ THE MAIL You can read the mail on a BBS or other station and get bulletins without connecting to that station yourself. You use this mode to do so. you will be prompted for the call whose packets you wish to monitor. Remember to enter the call of the station sending the packets, not the call of the one receiving them. (This corresponds to 'MONITOR 0' and 'MBX' callsign). This mode only works on the PK-232. You can also use this function to monitor both sides (read the mail) on a QSO on a busy packet channel. You may want to turn the Digipeat Data Display mode off when reading the mail. The Packet Terminal mode of operation will be shown in the Status window at the top of the screen. If you are reading the mail on a station, the callsign of that station will be shown next to the word "MAIL". If you are connected to someone, the call (and path) will be shown prefixed by the "*>" sequence. 3.2.4.5 Multiple Connect Modes. You also use this function to go into and out of the multiple connect mode. The default condition is one connect at a time. Should you opt for the multiple connect mode, make sure you know what you are doing. When you enter a multiple connect mode, the program will change the stream change character or the CHSWITCH character (in the case of the TNC from a default $00) to the '\' (backslash). At this time don't transmit raw directory files in or you will see an error message. You don't have to be in the command mode to use the CHSWITCH character. Read all about CHSWITCH in the TNC manual. When you return to the single user mode the program will reset the stream character to the default $00. When you are in a multiple connect mode, an asterisk will be shown in the status window next to the word 'PACKET'. PK232COM supports two multiple connect modes, individual and conference. An extract of an actual 'off the air' CRT display PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 18 (showing received text only) in a multi user mode is shown below. Note each line of text as received by the TNC is prefixed (by the PK232) with the IO channel number and callsign of the station its connected to . 1:4X4IL: *** CONNECTED to 4X4IL via 4X4IC, 4X6JP 0:4X4IC: joe do u read? 2:4Z4ZB: *** CONNECTED to 4Z4ZB 1:4X4IL: Look for me on PR via 4X6JP 73s and Shalom. 2:4Z4ZB: GE JOE I WILL DIS THEN U CAN GO VIA THE REP....> 1: *** DISCONNECTED: 4X4IL via 4X4IC, 4X6JP 0:4X4IC: UNPROTO CQ 2:4Z4ZB: GO AHEAD BOYS...DE ALON..> 0:4X4IC: 2: *** DISCONNECTED: 4Z4ZB 3.2.4.5.1 The Individual Multi Connect Mode. This is the normal Multi Connect Mode as described in the TNC manual. Here you are connected to up to 10 stations and will send different traffic to each of them. Each time you wish to send something to a particular station, you must select the IO channel the station is connected on before typing the text or sending the file. You select the channel by typing the '\' character followed by (in the TNC) the channel number. For example if you are connected to G8BTB on IO channel 0 and to G3ZCZ on IO channel 1, then to talk to G8BTB you would type '\0' before any text, and similarly to send something to G3ZCZ you would type a '\1' before the text you're going to send me. If you are not using a PK232, read the TNC manual to determine if the IO streams are identified by numbers or by letters. The TNC2 standard configuration uses letters. 3.2.4.5.2 The Conference Multi Connect Mode. In the conference mode on the other hand, everything that you type at the keyboard is transmitted to each station that you are connected with. Thus if you are linked to two stations each line will be packeted twice by the TNC. You don't have to worry about sending the wrong thing to the wrong person, as they will all get the PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 19 stuff. 3.2.4.5.3 The Bridge Multi Connect Mode. In the Bridge Multi Connect Mode you are acting as a central switch. You can link together up to 10 stations in one multi way connection. In this mode any packets arriving on any steam are echoed to all other streams that you have 'connects' on except the one that they came in on. Any- thing you type will be sent to all connected streams. In this manner, all stations will not see their own text echoed back. Each line of text output by PK232COM in this mode will contain the callsign of the station originating the packet. Your packets will contain your call as entered in line 1 of the PK232COM.SYS file. Thus for example, if your call was KB8RP/4X and normally shows up in the packet header as KB8RP here it will show in the data as KB8RP/4X. You can only enter the 'bridge' mode from the conference mode, and any station dis- connecting, will drop the bridge. You will then have to reset it from the key- board using the relevant function key. 3.2.4.5.4 Entering the conference mode. You enter this mode by selecting the 'F' option in the terminal mode select menu (Function key Alt 4). You terminate the mode by selecting the '1' option. 3.2.4.5.5 Connecting in the multi user mode. You connect in the usual manner using function key 7. You MUST WAIT FOR A CONNECTION TO BE ESTABLISHED OR TIME OUT before attempting to connect to the next station. If you do not, you will get an error message back from the TNC. In the conference mode, as the same text is transmitted on all IO channels, the throughput will thus be reduced, slow down your typing speed or use short packets. Should you use function keys alt 3 or 5 to check the link status or call monitored list, you may not be able to get back into the PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 20 converse mode if you have too many packets outstanding. If that happens, wait a while and then try to set the converse mode with function key 10. You may have to try it a few times, depending on how good your links are. DON'T TRY TO SEND A FILE IN THE CONFERENCE MODE, ITS NOT DESIGNED FOR IT. KEEP THE PACKETS SHORT. The conference mode will only work in the PK-232 if DCDCONN is set to ON. So if you are using a PK-232, PK232COM will do it for you when you enter the conference terminal mode in case you forgot or/and haven't set the PK232COM.SYS file to include the line 'DCD ON', At the same time set PK232COM.SYS default states to show the calls of other stations on each incoming line in the multi connect modes. (Read the TNC manual for how to do this). The conference mode will only work in the TNC2 if DCDCONN is jumpered so that Pin 8 of the RS-232 Interface changes state when you connect to someone else. If you get error messages and see the characters '\J' on your screen, then the jumper probably isn't set. The conference mode does not work on the TNC1. In the conference mode, if any one of the stations disconnects, the TNC will return to the command mode, and you must use function key 10 to return the program to the converse mode before you type another character of text. After setting the terminal configuration mode, it returns you to the TNC command mode. In the AMTOR communications mode you can do several things as follows; 3.2.4.6 FEC Places the terminal into the FEC transmit mode. This puts you on the air, anything you type will be transmitted. 3.2.4.7 ALISTEN Read the Mail on a QSO. Unfortunately, when you tune in a chirpy AMTOR QSO in the ARQ or standby mode you won't get any copy on the QSO in progress. You can however read the mail on one by entering the ALISTEN mode. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 21 3.2.4.8 ACHG Force a changeover or 'break in'. If for any reason you want to interrupt the other station you send a 'BREAK' signal in software this way. 3.2.4.9 ARQ Return to the ARQ standby mode. You must be in this mode to receive signals from another station who is calling you. You may do it this way or via the main Mode Menu. When you tune for CQ calls, they sound somewhat like fast RTTY with a ringing sound similar to the connect alarm (but at a faster ringing rate) used by PK232COM. 3.2.4.10 Force LETTERS Case This function lets you force the receiver to the letters case if for some reason you appear to be in the numbers case. It will return you to the converse mode. 3.2.4.11 Override ROBOT Mailbox/Beacon This function lets you override the ROBOT BEACON and chat to a station that has linked to the ROBOT. Use it after the message in PK232COM.TXT has been sent, ie when the other station is sending a message to you. 3.2.4.12 Turn on Mailbox/Beacon. This function lets you turn on the Mailbox during a regular AMTOR QSO so that the other station can leave a message or download a file remotely. 3.2.5 Monitor Channel Activity This function lets you see what calls the TNC has heard recently on the Packet channels. You can see up to 18, with the data and time they were last logged by the TNC. If they were heard directly an asterisk (*) will be listed next to the call sign. If they were heard being re transmitted via another station, the asterisk (*) will not be shown. Refer to the 'MH' command in the TNC manual. If you are not using a PK-232 refer to the MH command in the TNC manual for the particulars of the display. The MH list shows up in a special window and freezes until you depress any key. While the list is frozen, PK232COM is not monitoring received data, so PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 22 don't freeze it too long. This function does not work on the TNC1. 3.2.6 Change Packet Connect/Contest Message 3.2.6.1 Change Packet Connect Message This function allows you to change the message that will be received by another packet station when it connects to you. Refer to the 'CTEXT' command in the TNC manual. 3.2.6.2 Change Contest Message This function first toggles the contest mode. If the contest mode is active, the word 'TEST' and the number of the next QSO will be displayed in the status window. When the contest mode is toggled on, this function then allows you to set the starting QSO number and write in the non changing or standard message that will be transmitted as part of an exchange of messages during a contest. The contest function is toggled off the next time you select this function, or when you change the PK-232 Communications mode (ie. switch from Morse to BAUDOT). Note that while this does give you some semi automatic contest operation by using function keys, there is no checking of callsigns for duplicates built into the program. In a contest, you enter the callsigns and call the other station in the normal manner, then use this function key to transmit the exchange. In Morse, and RTTY don't forget to use function key 10 to turn on the transmitter first. 3.2.6.3 Change CQ text Message This function allows you to change the contents of the CQ text message string. This is the string that is transmitted along with the CQ call. The default value is loaded from the PK232COM.SYS file. 3.2.7 Enter Call Sign This key lets you enter the call of any station calling you into the program. If you type the enter key in response to the prompt, you can later use the F3 (function key 3) to transmit the sequence "de <yourcall>". You may also use the Shift F7 key to PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 23 call that station in the non AMTOR modes. In AMTOR, you use it to enter the callsign of the station you want to or have called by means of the SELCAL. You should also use this to enter a callsign of a station that called you, if you were not in an autoCQ mode. 3.2.8 Not used. You don't want to disconnect accidentally if you just depress function key 8 without the 'Alt' key. 3.2.9 Activate Transmit Buffer The use of this key sets PK232COM to the "Type Ahead" mode. Any characters then typed at the key- board will be placed into the TNC transmit buffer. The contents of the buffer will be transmitted over the air when the transmit function is invoked [FK10]. This feature allows you to 'type-ahead' as you can enter text into the transmit buffer while viewing incoming words in the INPUT window in the screen. Any characters typed from the keyboard will be echoed in the OUTGOING window on the screen. THIS FUNCTION IS NOT ACTIVE IN THE AMTOR or PACKET modes. Packet is full duplex, while in AMTOR the PK-232 buffers the data until you receive the next +? sequence. 3.2.10 Help The use of this key will activate the HELP menu in a different window on the screen. This window will remain on display until a character is typed at the keyboard, or a character is received by the computer from the PK-232. 3.3 Shift Function Keys 3.3.1 Dir This function shows you the directory of the logged in (active) disk drive. 3.3.2 Rename This function allows you to rename a file. You could for example rename a document file to a "callsign.OUT" file so that someone will receive it PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 24 automatically next time they connect. 3.3.3 List of Outgoing Messages This function shows you the outgoing messages that have not been sent. In other words, all files with the file extension of '.OUT'.See below for a description of outgoing messages in your "Packet Radio Answering Machine". 3.3.4 Delete This function allows you to delete a file 3.3.5 List of messages that have been sent. This function shows you the messages that have been sent. In other words, all files with the file extension of '.OLD'. 3.3.6 Mail Beacon Activate Using this function will also load a QTC 'Mail' list into your Packet communications mode Beacon and initiate a beacon transmission every 30 minutes (Refer to the BTEXT command in the TNC manual). If no mail is pending, or the only message is to you (incoming or snatched), beacon transmissions are inhibited. This conforms to good operating practice on crowded Packet channels. 3.3.7 Retry This function allows you to retry a connect that for some reason did not go through the first time. It save wear and tear on your fingers particularly if the desired connect path is via a number of digipeat relays or through a number of NET/ROM NODES. In the non packet modes, it allows you to retransmit a call to another station without having to reenter the call (FK7). 3.3.8 Toggle Conference Bridge ON/OFF. This key toggles the conference bridge on and off. See section 3.2.4.5.3 for how the bridge works. Just remember that the bridge puts out a lot of packets, so do multi way connects on a quiet frequency. You must be in the conference mode to turn the bridge on, and any disconnect will take the bridge down. Should that happen, toggle it on again. A bridge will be shown in the status window whenever the conference bridge is up. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 25 NOTE: THIS MODE MAY NOT BE FULLY DEBUGGED. YOUR COMMENTS ARE REQUESTED. 3.3.9 Connected Indicator Reset. You use this function key to reset the PACKET and AMTOR beacon mode "connect has taken place indicator". This is a flashing [C] display in the status window. Whenever someone else connects or links up to you this display will be activated. It is reset by this function key. If you are monitoring Packet traffic on a channel, you may not notice that a connect has previously taken place. This indicator alerts you to check the contents of the PK232COM.RUN disk file for any incoming messages. The number shown with the 'C' is the number of connects that have taken place since the Indicator was last reset. If a 'happy face' is flashing along with the connect count, your "target station" was amongst those connecting. 3.3.10 OVER function. In the Packet communications mode this function sends your callsign followed by the > and Line feed characters. You may use this to signal 'OVER' in a packet contact. In the AMTOR communications mode this function sends a callsign sequence followed by the '+?' sequence of characters which are the software 'OVER' signal. In the MORSE and RTTY (Baudot and ASCII) communications modes, this function lets you transmit the following sequence <other call) DE <your call> and returns you to the PK-232 Command Mode. For example if you are 4X6AA and you are working G3ZCZ then this function would transmit the sequence 'G3ZCZ de 4X6AA'. You use this at the END of a transmission in any mode except Packet. If you have typed something into the 'type ahead buffer' then touch this function, the contents of the buffer will be transmitted followed by the call- sign sequence. 3.4 Control Function Keys 3.4.1 Day Flag This function key puts the TNC into the command mode and loads the date into it from the computer. You use this to reset the TNC clock if it isn't that stable, or to flag a date and time into the log file when in the non Packet modes. For example if you PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 26 want to time tag a qso. This function does not work on the TNC1. 3.4.2 CWID This function key is used to send a CW identification when operating BAUDOT, ASCII or AMTOR. You use this if your license requires you to identify in morse code as well as in the operating mode. In AMTOR, the CWID is sent in the FEC mode. The identification consists of the sequence 'DE <your callsign>' where your call sign is that entered into the PK-232 as 'MYCALL'. 3.4.3 Message Upload PK232COM contains store and forward routines for messages in a Local Area Network (LAN) as described in Appendix 2. Use this function to upload a message to another system compatible with PK232COM. When you invoke this function, the computer will ask you to tell it if you want to leave a note, QSP or QRU. 3.4.3.1 Leaving a Note in your system. In all modes you can leave a brief note (message) for another station. When you invoke this function the header is written to the message file, then as you enter the text it is stored on the disk in the usual format. WHILE WRITING YOUR NOTE, ALL OTHER FUN- CTIONS OF PK232COM ARE INHIBITED OR LOCKED OUT. THUS IF SOMEONE CONNECTS TO YOU, THE TNC WILL KNOW THAT BUT PK232COM WILL NOT. BE WARNED !!! After you have left the note and received the 'QSL' message from PK232COM, if you are in the Packet communications mode, push function key 8 or function key shift 6 to load the callsign of the recipient into the beacon. When you leave a note, leave it for the root call, for example to leave a note for KL7LF/KH3 leave it for KL7LF, similarly to leave a note for WB8WKA-1 leave it for WB8WKA. PK232COM is smart enough to extract the root call from any callsign it PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 27 links/connects to. 3.4.3.2 Leaving a message on an other PK232COM system [QSP]. The QSP function lets you enter the callsign of the station you wish to leave a message for. It will then send the text sequence :QSP: <callsign>. The other PK232COM HOST station will either reply :QNO: followed by a number or :QRV: <cal- lsign>. The 'QNO' message means that the other computer cannot accept the message, the :QRV: message means that it is waiting for you to send it. If you get the :QRV: reply, go ahead and type the message, or send the text file containing the message. If you type the message, use a control Z (^Z) character and carriage return to terminate the message. (In AMTOR, PK232COM will trans- late the ^Z to :EOF: +? to terminate the message). You will then receive either a :QSL: from the other station meaning that the message is accepted, or a :QNO: followed by a number which means that something went wrong and the message was not stored. 3.4.3.3 Uploading messages to another PK232COM system. The QRU function allows you to upload a number of messages to the other station. You use it when you have messages pending on your system and want to pass them to a third computer for storage in the network, while you take your computer off-line. You can only use this function with a station designated as a store and forward mail box, for which you have set up a <callsign>.MBX file (see section 7). This function may be triggered by you using this control key or by the connecting station sending you a :QRU: command. When the sequence is over, the computer sending the messages will transmit the NC/L command word :QJG: to signal that the sequence is complete. Should you receive it before you get any messages, then there weren't any pending. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 28 If you want to download messages from another PK232COM system, connect to it and type the sequence :QRU: followed by the 'Enter' character. That system will then respond to you as if the operator there had initiated a QRU function. Appendix 2 contains more information on the LAN capabilities of PK232COM. 3.4.4 Show last few log entries. This function displays the log entries made during the active session. If no QSO's have been made since the program was loaded the display window will be blank. Up to 5 log entries will be displayed in the window. You use this function for a quick look at which stations have connected to you in your absence. 3.4.5 Automatic CQ Sender This function will send a CQ sequence, wait about a minute or so and then repeat the CQ sequence every minute or so until it receives your call back from someone else. When it does so, it will alert you with a Connect Alarm signal and reset to the normal or listening mode. When the Automatic CQ sequence is in operation, an indication will be shown in the status window. The display will be constant while the transmitter is sending the CQ test, and will blink while the receiver is listening for a reply. The time delay between calls is set using The Control Function key 7. The automatic CQ function will only work in the PK- 232 non Packet modes if the 'EAS' mode is set to 'ON' per the PK232COM.SYS file. In other words, you must be able to see the CQ text pop up in the out- going window and then slowly echo in the incoming window for the function to work. The reason for this is that the "K K K" sequence is used to arm the software to look for your callsign. If it wasn't, the program would recognize your call being echoed to the screen and think that you had called yourself. In AMTOR you will get the connect alarm only when the replying station transmits the '+?' character combination. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 29 The check for the detection of your callsign and the connect alarm sequence only occur after a line feed character have been received. Under most conditions in AMTOR, many in RTTY, and some in MORSE, PK232COM will recognize the callsign of the station answering your CQ and display it in the status window. In the event that it fails completely, the sequence '--?--' will show up in the status window. Since the recognition algorithm use just look for the first word following the 'DE ' sequence and assumes that it has the callsign, be careful to check it when operating under QRM conditions. You can override the automatic call selection with the Enter Callsign function key. The automatic CQ sequence is cancelled when an incoming call is detected, you push the disconnect function key, or if you change communications modes. 3.4.6 SELCAL This function key toggles the SELCAL feature on and off. When the SELCAL is activated, as shown in the status window, the incoming text from the TNC is scanned. When either the letters "ZCZC" or 'your callsign' (as entered in line 1 of the PK232COM.SYS file), the capture-to-disk is turned on. All subsequent text will be stored in the PK232COM.RUN disk file until the letters "NNNN" are received. At that time the capture-to-disk is turned off. You may use this feature when monitoring commercial RTTY broadcasts to record news and other information, or when calling CQ to start recording all incoming text and keep the QSO on disk. You may use the loggletoggle function to override the automatic turnoff if you wish. 3.4.7 Beacon Toggle On/Off/CQ delay time set. This function toggles the beacon option for the automatic CQ caller in the AMTOR and Packet communications modes. When active and CQ is being called, a [B] will be displayed in the status window. In this mode, the Automatic CQ sequence will resume after the AMTOR link is dropped or a Packet Communications mode disconnect. In the beacon mode, the last few logbook entries will be displayed in the logpage window which over- lays the outgoing text window at the bottom of the screen. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 30 In the Packet mode, the CTEXT message is the only transmission from you that the other station will receive, so make it good. In the AMTOR Mailbox/Beacon mode, the contents of the PK232COM.TXT file will be transmitted to the station who called you. The capture-to-disk will then be turned on to record one transmission from that station. The QSO will then be logged to the logbook file. Don't forget to check the entries in case the computer made a mistake in recognizing the call sign of the other station. THE BEACON MODE IS DESIGNED TO ENCOURAGE PEOPLE TO QSY OFF THE CROWDED PACKET HF CHANNELS. DO NOT USE IT ON A CROWDED HF CHANNEL OR ON AN ACTIVE VHF CHANNEL. IF YOU DO, YOU WILL SOON FIND THAT OTHER STATIONS HAVE SET THEIR TNC'S TO REJECT YOUR PACKETS, YOU WILL NOT WORK ANYBODY, YOU WILL JUST BA A SOURCE OF QRM AND WILL BE KNOWN AS SUCH. THE MODE IS ALSO DESIGNED FOR ROBOT BEACONS FOR THE HIGHER FREQUENCIES. FOR EXAMPLE IF YOU LEAVE IT RUNNING ON 10 METERS YOU NEVER KNOW WHEN A SHORT OPENING WILL ALLOW A QSO TO SOME PART OF THE WORLD. A DX CONTACT YOU WOULD HAVE MISSED OTHERWISE. DO NOT LEAVE IT RUNNING ON 20 METERS WHEN THE BAND IS OPEN. YOU WILL JUST BE CAUSING QRM. FURTHER APPLICATIONS ARE IN METEORSCATTER AND OTHER "EXOTIC" MODES OF COMMUNICATIONS. If you are using this mode in a special event station or DX-pedition you may type characters into the transmit buffer, while the other station is sending to you. When he, she or even it turns it back to you, you will transmit those characters before the sign off sequence. In both the Packet and AMTOR communications modes, the robot may be shut down by stations connecting to you and telling you to QRT. 3.4.7.1 Beacon Mode Toggle/On-Off This function allows you to toggle the Beacon mode on and off. 3.4.7.2 CQ Delay Time Adjust This function allows you to change the time that the program waits for a response after a CQ call until the following one is transmitted. The default value is loaded from the PK232COM.SYS file. You may want to experiment since the actual time will PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 31 depend on the clock frequency of the computer. Make it a small number such as 4 or 6 when operating AMTOR or a DX- pedition, and make it a larger number such as 30 when operating on crowded packet channels. The maximum allowed value is 255. 3.4.8 Not used. You don't want to disconnect accidentally if you just depress function key 8 without the 'Shift' key. 3.4.9 Transmit Buffer Clear This function is used if the PK-232 continues to transmit the characters you put into the 'type ahead buffer' after you have tried to shut it down. 3.4.10 Logbook. PK232COM performs automatic logbook entries for Packet and AMTOR Beacon mode Connects, and semi automatic logbook entries for other modes. The Log file is compatible to that of the CONTEST program in the G3ZCZ PC-HAM package and can be processed by the DBASE Logbook Package of PC-HAM by G3ZCZ for indexed listings, tracking of DXCC and other AWARDS, etc. This is ideal for special event stations and DX-peditions, for the whole QSL process and further statistical analyses of their operation has been automated. For this function to work, the file PK232COM.LOG must be present on the disk. If it isn't, it will be created for you. After one logging operation has occurred, edit out the initial text. You must perform this editing operation before appending the contents of the logbook file to the logbook database of the PC-HAM LOGBOOK Package. Edit the log before appending it to the DBASE package, as there may be some null characters at the end of the file which may be recognized as a blank entry by DBASE. When you edit the file, replace all the commas by the three character sequence "," (quote, comman, quote). It is also advisable not to let the each of the files get too big. When an AMTOR beacon mode or packet connect occurs, the connect is automatically logged. The connect path is placed in the comments section of the logbook entry. In the non packet modes, the log PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 32 data entry is set up for you with default 599 values for the reports exchanged. You invoke this function to enter the data into the log. When you invoke the function you will be presented with the following typical menu in the menu window. LOG ENTRY DATE TIME CALL BND TX RX MODE POWER S R COMMENTS 87/04/27 17:28 20 599 RTTY 10 - - Date,tIme,Call,Bnd,Tx,Rx,Mde,Pwr,qSl snt,cOmmnts or Logit (*) ? You should reply with the capitalized character associated with each item. For example, if you want to change the Band, enter the letter 'b', to change the cOmments, enter the letter 'o'. Touch the 'ENTER' key after you have made your choice and enter the text when prompted. You will then be presented with an updated entry. To enter the data into the logbook, use the 'l' key, to save the data but not make a log entry use the '*' character. You would do that if you want to change the band or power information. You may use the 'qSl sent' entry to tag the fact that you have written out a QSL card. The band and power information are set up from the default values stored in the configuration file PK232COM.SYS. They are displayed in the status window. If you are using the logging function, you should change them when changing bands/powers and quit the logging function with the '*' character so that you don't put a blank entry into the logbook. Note that you can also use this function to enter the odd SSB contact into the logbook file. If you do, use the characters 'SSB' or 'FM' for those voice modes to remain compatible with the rest of the DBASE logbook package. NOTE Do not use the comma character ',' in the comments field. If you examine the log entry you will see that all items are separated by comma's. If you use a comma character in the comments you will screw up the transfer of data into the logbook package. The comments field in the logbook is restricted to a maximum of 10 characters. If you try and enter more than 10, the surplus will be ignored. When you examine the DBASE logbook file, if it looks funny or the data are in the wrong, place, then you PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 33 probably have the wrong number of comma characters in some line. Delete the .DBF file and reedit the .LOG file, to make sure that there are the correct number of comma characters. You will recognize the pattern readily enough. 3.5 Shift/Baudrate Control keys The following keys are used to control the Shift (Wide or narrow) and the Radio link baudrate in the BAUDOT, ASCII and PACKET communications modes. 3.5.1 RIGHT ARROW speeds up the baud rate. 3.5.2 LEFT ARROW slows down the baud rate. 3.5.3 UP ARROW toggles the shift from Wide to Narrow and back. 3.5.4 DELETE toggles the USOS function. In the PACKET mode the baudrate may be changed between 300, 600, 1200 and 2400 bauds. In the other modes all baud rates supported by the PK-232 may be selected. The state of each of the above functions are displayed in the status window at the top of the screen. If USOS is active, 'USOS' will be shown. The shift is shown as 'W' or 'N' for wide or narrow respectively. 3.6 Additional keys 3.6.1 The HOME Key The home key will clear the window screen that the cursor happens to be in at the time that the key was depressed, and will then position the cursor at the top left hand corner of that window. 3.6.2 The DOWN ARROW key The DOWN ARROW key toggles the Normal Reverse Sideband function in all communications modes except MORSE. The sideband is depicted in the status window by the up and down arrows. If the down arrow is showing, you are set for Lower Sideband (LSB) which is the normally used one. If you have reversed the sidebands a flashing up arrow will be displayed. If you set your transceiver to LSB you will be set correctly for all modes. For CW operation you may set your rig to the CW position and ignore the sideband setting. If you use FSK just set it so that it works for you. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 34 3.6.3 The Alt A key (Alert toggle). This key toggles the Alert call function on and off. If it is off, you are prompted for the call to be monitored, if it is on, it is turned off. The toggle is set when you enter a callsign, and cleared when you depress the 'Enter' key instead of a callsign. The Alert call will be shown flashing in the status window when in the disconnected state. The Alert function is used in the Packet communications mode when disconnected and the terminal set for 'TRFC' or 'CQ/BEACON'. PK232COM will scan the packet headers received from the TNC, and, when it sees a packet originated or digipeated if the MRPT parameter in the TNC is set to 'ON', (the default state in PK232COM.SYS by the way) by the station whose call you have entered as the 'Alert' call, it will sound an alarm at the console. NOTE: If the terminal is set for 'CQ/BEACON' the Alert will only sound if the specified station transmits CQ or BEACON packets. 3.6.4 The Alt B key (Baudot/ASCII Baud rate set). This key allows you to set a desired communications baud rate directly. You will be prompted to enter the desired rate. Use this function to avoid having to shift through too many intermediate states, if for example, you want to make a direct change from 45 to 100 bauds. 3.6.5 The Alt C key (connect request). This key performs the same task as Function Key 7. The Alt C key has been provided for those people whose fingers have learnt YAPP and don't wish to be reeducated. 3.6.6 The Alt D key (disconnect). This function key returns the station to the receive communications (TNC command) mode. It may also be used to abort the automatic CQ sequence. If you use it to abort a CQ sequence while the transmission is in progress, flush the PK-232 transmit buffer using Control function key 9. In a multi connect situation the program will prompt you to tell it which IO channel to disconnect. In AMTOR this function key toggles PK232COM between PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 35 the Chirpcopy mode (listening to a QSO in progress) and monitoring FEC transmissions (CQ calls). This key performs the same task as function key 8. 3.6.7 The Alt F key (Digipeat monitor toggle) This key toggles the digipeat display function on and off. If the Digipeat Display Function is active, any signals digipeated through you will be stored to the PK232COM.RUN file and a 'beep' will be sounded for each packet being digipeated. The status display window will also show a [D] at that time. The MDIGI function is set 'ON' when the Digipeat display function is 'ON', this means that digipeats will show up while you are connected to someone. The default state for the Digipeat Display Function is OFF. 3.6.8 The Alt M key (Mail Scan). This key allows you to scan messages in the computer. After depressing the key you will be prompted for INcoming or OUTgoing (I/O) messages. If you request Incoming messages you will see the messages addressed to your callsign. After scanning your messages, the file will be renamed to yourcall.n. where n is an incrementing number from 1 to 999. Should you choose to scan messages addressed to other stations, they will be displayed but otherwise not be affected at this time. 3.6.9 The Alt P key (Printer Toggle). This key toggles the printer on and off. When the printer is turned on, any incoming data will be printed in real time. If you intend to print files received at 1200 bauds in the packet communications mode, use a print spooler or you may loose data. The printer is automatically turned off in the packet mode when a disconnect occurs. 3.6.10 The Alt R key (Message Relay toggle) This key toggles the Store and forward Message Relay Capability of your system on and off. If the Message Relay Capability is active (toggled on), any one who connects can store a message in your system using the ':QSP: <callsign>' NC/L function. If the Message Relay Capability is not active (IE. toggled off) anyone who attempts to ':QSP: a message' will receive a ':QNO: 1' "error" message. The status display window will show a [R] when the Message PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 36 Relay Capability is active. The default state for the Message Relay Capability is loaded from the PK232COM.SYS file. When the Store and forward capability is active, the suffix 'R' will be added to the '*** PK232COM 1.42' message received by anyone connecting to your system to notify them that they can store messages. In this manner they don't have to try to leave a message and then get ':QNO: 1' error message to find out if the feature is toggled off. 3.6.11 The Alt S key (Sound Set/Toggle). This key toggles the sound on and off. If the sound is off, a flashing indicator will be displayed in the Status Window. When the sound is toggled on again, a chime will sound to verify the audio. 3.6.12 The Alt T key (Target Call set/toggle). This key toggles the Target call function on and off. If it is off, you are prompted for the call to be monitored, if it is on, it is turned off. The toggle is set when you enter a callsign, and cleared when you depress the 'Enter' key instead of a callsign. The Target call will be shown flashing in the status window when in the disconnected state. The Target call function is used in the Packet communications mode when disconnected. PK232COM will monitor the stations connecting to you. When it sees a connect by the station which you have entered as the 'Target' call, it will set the flashing Connect Count display to show a 'happy face'. 3.6.13 The Alt X key (Exit or return to DOS). This function is the same as the Alternate Function 1 key. It exits the program and returns you to DOS. When you exit the program, the TNC is put into the VHF default mode in which it rejects calls from any other stations. (Read about the 'CFROM' command in the TNC manual). you can thus if you wish leave it powered, and if you also leave the VHF radio powered up, you will be active as a digipeater, but at the same time anyone trying to connect with you will receive a busy signal. The MBX function (Reading the Mail) is also cleared at this time. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 37 3.6.14 The Alt Z key (BBS Mail download). This key initiates a BBS mail download sequence. It initiates the same sequence as the BBS_Mail_Snatch. You use this key if you connect to a BBS before you hear its beacon, or if you have disabled the BBS_Mail_Snatch feature. This key must be used ONLY when connected to the BBS and BEFORE the first '>' is received. Note: it is that first '>' that triggers the sequence. If you have already received that first '>', send the BBS any command, and the sequence should begin when the BBS signals that it has completed processing that command. The sequence performed by the BBS_Mail_Snatch is as follows: RM To read your messages, L To let you know what is new on the BBS, LM To list ALL your messages on the BBS, B To log you off the BBS. PK232COM will wait for the '>' as the last character of the line of text being received from the BBS, before issuing the next command in the sequence. Your messages will be placed in a message file <yourcall.OUT> as if someone else had left a message for you. When you use this function you will be asked if you want to upload or download. If you want to download, just push the 'Enter' key. A Download (Mail from the BBS to you) will automatically be followed by an Upload if the *.BBS file exists. 3.6.15 The PgUp key (Scrolls back incoming text). This key lets you repeat the display of incoming text which has scrolled out of the incoming window. you may print it or capture it to disk during the repeat. 3.6.16 The Control Z key. This key is used in the Packet communications mode to signal the end of a file or message, when loading messages into another PK232COM system or into a BBS. In the AMTOR communications mode, it is translated into the sequence ' :EOF: +? ' which can be used as a fast break-in changeover or to terminate a message being stored in another PK232COM AMTOR mailbox. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 38 4.0 PK232COM disk files The following disk files are associated with the program. 4.1 PK232COM.COM This is the program. You activate it from DOS by typing the word PK232COM followed by ENTER in the normal manner of invoking DOS commands. 4.2 PK232COM.RUN This is the file containing the captured incoming text. This file contains incoming data from the TNC recorded while the 'capture to disk' function was active. 4.3 PK232COM.SYS This file contains the configuration information for both the program and the PK-232. YOU MUST EDIT IT before you run the program on the air the first time. Use your word processor in the NON-Document mode. The contents of the file are as follows. 4.3.1 The first line. The first line contains your callsign. Please do not use G8BTB. Replace G8BTB with yours. You may use / characters if you wish. This is the call sign that will be used in the non- Packet modes. You may thus use "portable designators" such as G3ZCZ/A, G3ZCZ/W3 or G3ZCZ/4X, which you cannot do in Packet. IF YOU DON'T CHANGE THE CALL SIGN, YOU WILL GET AN ERROR MESSAGE AND THE PROGRAM WILL NOT RUN. This is the call that will be monitored for in the Digipeat monitoring mode. In this mode which is toggled on and off by the Alt F key, if someone uses you as a digipeater while you are not connected to anyone else, the event will be logged to disk. This mode will only work if your callsign as stored in this line is a valid (upper case only) packet callsign. For example, in the PK-232, if the callsign is G3ZCZ then the sequence >G3ZCZ> will be recognized as a digipeat and the event logged. Thus for example 4X6AA*>G3ZCZ>4Z4ZB would be logged as a digipeat event. Now if the callsign in this line is G3ZCZ/4X then the event will not be recognized as a digipeat PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 39 because the computer would be checking for a G3ZCZ/4X in the packet header and it would never see G3ZCZ/4X. This option is inhibited for reciprocal callsign operators due to the AX2.5 protocol itself. If you have a / character in your callsign, and use the base call for packet identifying the location in the CQ text, then the function will work if you place the "portable location" as a suffix. For example, if the call is G3ZCZ/4X and the packet identification is G3ZCZ, then the digipeat monitor will work. If the call was entered as 4X/G3ZCZ the digipeat monitor would check for 4X and would not appear to work. Store your callsign using UPPER CASE characters if you want this option to work (IE. G3ZCZ). If you use lower case (ie. g3zcz), the option will not be enabled as recognition will never take place. The PK-232 automatically converts case to upper case in the non packet communications modes. If you are using an SSID (eg. G3ZCZ-8) in the packet communications mode, you should enter the whole call INCLUDING the SSID. 4.3.2 The second line. The second line contains the AMTOR SELCAL configured for your callsign. You use it again later to tell the PK-232 what the SELCAL is. This line just tells it to PK232COM. You still need this line even if you are using a Packet mode only TNC. 4.3.3 The third line. The third line contains the line of text transmitted by the PK-232 in a CQ call (in any mode except for MORSE). Think of this message as a CQTEXT line. Edit this line as well. 4.3.4 The fourth and fifth lines The band and power information are set up from the default values stored in the configuration file PK232COM.SYS. They are displayed in the status window. If you operate on another band or your transmitter uses a different power level change the default values in the file to reflect your custom default state. The fourth line contains the band information. The default value is 2 for 2 Meters. Use the Meter value for the band to keep the display correct. The fifth line contains the value for the PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 40 transmitter power. The default value is 10 for 10 watts. 4.3.5 The sixth line The sixth line contains a number which tells the program how long to wait before transmitting a CQ call when in the beacon (automatic) mode. A value of 4 corresponds to about 2 minutes. This value of time will vary depending on the clock speed of your computer. You may have to experiment with different values. The default value is 0 which inhibits the beacon mode. 4.3.6 The seventh Line The seventh line configures the LAN store and forward capacity of the system also known as the Message Relay Capability. If it is a '0' (default state) your computer will not accept messages for forwarding. If it is a '1', it will. See Appendix 2 for details about LANs. Remember, if you configure your computer to store and forward messages, you have a moral obligation to deliver them. The status of this function shows up as an [R] in your status display and in the connect message which is transmitted to the other station at connect time, as an 'R' suffix to the message when active. 4.3.7 The eighth line This line contains the default Communications port. The default value is 1. You must leave it set to 1. THIS VERSION OF PK232COM CAN ONLY BE USED WITH COMM1. 4.3.8 The ninth line (TNC type) This line tells the program which TNC you are using. The PK-232 command set is slightly different to those of TNC2 in the packet mode. Thus the command dialog has to be changed somewhat to make the 'SOLO, TRAFFIC, CQ/BEACON and MAIL' terminal modes work correctly for different TNC's. NOTE that program does not check the TNC in the Non Packet modes, so for example if you try to set a TNC2 to AMTOR, PK232COM will send the PK-232 commands to the TNC2 which should then return an error message. Valid TNC's are PK232 KPC TNC1 PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 41 TNC2 (don't type the '.'). The TNC2 used to test PK232COM 1.41 was an MFJ 1270. The KPC includes software changeover from HF/VHF. Most TAPR TNC2 clones should work with the TNC2 setting. 4.3.9 The Tenth line (Terminal Baud Rate). This line tells PK232COM what baud rate the TNC is set to. This is the baudrate on the RS-232 line between the TNC and the computer. Valid baud rates for PK232COM are 1200, 2400, 4800 and 9600. If you specify something else PK232COM will default to 1200. If the TNC does not use an interrupt driven serial port you may experience problems when using baud rates greater than 1200. The PK-232 does not like baud rates faster than 2400, and sometimes not even that. Use 1200 until you have tested and are sure that a faster one will work. This program has been tested on a TNC2 using a terminal baud rate of 4800 bauds and worked correctly. 4.3.10 The eleventh line. The QTC _Snatch or Automatic Connect Attempt Flag. If the value entered on this line is a 1, then the QTC_Snatch Flag is enabled. if the value on the line is a 0, then the flag is disabled. If the QTC_Snatch flag is enabled, PK232COM scans the contents of packets appearing in the Inwindow on the screen while the terminal is disconnected. Should it recognize the three text strings 'PK232COM', ':QTC:', and 'your callsign' in the packet, it will then issue a connect request to the callsign of the PK232COM station that originated the beacon transmission. If the connect is made, the other station will send you the message automatically which PK232COM will capture to disc. The connect will time out and terminate a few minutes later. Hopefully it will not try to connect to you if it hears your beacon with your call in it (someone left you a message) via a digipeater. The normal connect request will be made DIRECT to the station. A digipeat path will not be invoked as this feature is designed to trigger a normally silent station standing by on the LAN (good PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 42 operating practice). If you expect messages from stations you can only connect with via a digipeater, place the path in your PK232COM.DIR directory file. It should be there anyhow if you connect to the station regularly. For example, if you expect messages from 4Z4ZB whom you can only work if digipeated via 4X1AA then place an entry like 4Z4ZB 4Z4ZB V 4X1AA in the PK232COM.DIR file. The QTC_Snatch leaves your messages in a message file <yourcall.OUT> (PK232COM 1.46+). It is trig- gered by the first > in the initial connect response of PK232COM 1.46R> (note the '>') and terminated by the 'over' at the end of the message ie. G3ZCZ/W8> (note the '>'). If you train stations not using PK232COM who want to leave you messages to trigger your QTC_Snatch, by transmitting the following unaddressed packet 'PK232COM :QTC: YOURCALL', your system will connect to them. (For example to leave a message for me, they would send 'PK232COM :QTC: G3ZCZ ' as an unaddressed packet [in converse mode when not connected, or in their beacon text].) If they then send you a '>' on a line by itself, followed by the message itself, and terminated by an other '>' as the last character of the line, the message will end up in a message file rather than in the PK232COM.RUN file and you can scan it fast using the Alt M key. It goes without saying that the message itself should not contain the '>' character. If it does,by the way, the first part of the message will be in the message file, while the remainder will be in the PK232COM.RUN file. 4.3.11 The Twelfth Line. The BBS_MAIL_Snatch flag. This line controls the BBS_Mail_Snatch. If the BBS_Mail_Snatch is enabled, when a BBS sends a packet announcing 'Mail', if your callsign is in the first line of that message, PK232COM will issue a connect request (again via the path in PK232COM.DIR) to that BBS. If connected, it will send the following sequence of commands to the BBS, while waiting for the '>' as the last character of the incoming line, each time. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 43 RM To read your messages, L To let you know what is new on the BBS, LM To list ALL your messages on the BBS, B To log you off the BBS. Your messages will be placed in a message file <yourcall.OUT> as if someone else had left a message for you. See the Alt M key and Section 4.8 on the *.BBS to see how you can also read other messages and upload messages as part of the BBS_Mail_Snatch. NOTE: If you are not using a TNC1 you MUST set the TNC HEADERLN parameter to ON. The packet headers and the text of the packets must show up on your screen on separate lines. 4.3.12 The Remaining lines. The remaining lines contain commands to the PK-232. For further information about them refer to the TNC manual. The example in the PK232COM.SYS file is as follows. CONSTAMP ON CHCALL ON CHDOUBLE ON CMSG ON CTEXT SHALOM you have connected with G3ZCZ/4X daystamp on DCD ON eas on echo off headerln ON flow off mycall G8BTB MYALIAS JOE MYSEL GBTB newmode on NUCR ON nulf on users 1 usos on If you use a different TNC (other than the PK232) you will have to edit this command list. 4.4 PK232COM.LOG This file contains the log entries. It will be created automatically to initialize the logging function. The format of the logbook file is the same as that created by the G3ZCZ CONTEST.BAS program and both files are designed to be appended into the G3ZCZ LOGBOOK DATABASE package presented as part of PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 44 the PC-HAM software package. It should be edited with a word processor in the non document mode to delete the first line and clean it up before the file is appended to the DBASE logging package data files. 4.5 PK232COM.DIR This is a directory file. You use it to store connect NET/ROM or digipeat paths as well as name/callsign relationships. Examples are Joe G3ZCZ Alon 4Z4ZB V 4X6AA Milt 4X6AA LR 4X6LR hf-il 4x4hf v 4z4zb 4x4il hf-rj 4x4hf v 4z4zb 4z4rj You create this file with your wordprocessor in its non document mode. You must leave AT LEAST one space character between the first (key) word and the connect path. When you type in the key word, the program does not care about upper or lower case. If the program does not find the key word, it will try to connect with whatever you typed in. If you already have a YAPP.DIR file just rename it to PK232COM.DIR. An example of a PK232COM.DIR entry for a NET/ROM path is K1HTV ELK v WB4APR-5! SNJ3! NNJ! WMA! SCCT! K1HTV where the '!' separates each stage of the link. Consider the manual sequence to make the connection. K1HTV is the station the contact is being attempted with, and he is located within range of the SCCT NET/ROM node. The station attempting the connect is located in the Washington DC area one digipeat away from the ELK NET/ROM node. The connection to the local node is performed first. The operator has to type ' C ELK v WB4APR-5' to make that link. When the connect with the node is achieved, the operator must type 'C SNJ3' to connect to the next node. Each time the connection is made, the operator must type in the command to make the next one, until finally the last node is reached and a connect request can be made to the destination station (either direct or via a digipeater). Sometimes there may be an intermediate non NET/ROM connection between two stations somewhere in the path. This procedure is tedious and time consuming, because it may take several seconds to complete each stage of the link. PK232COM automates this sequence by scanning the line in the PK232COM.DIR file associated with the key callsign and PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 45 transmitting each section of the line when it recognizes the 'Connected to ' reply from each NET/ROM node in the path. When it finally gets to the destination it sounds a chime to alert you that the connect has been achieved. If for any reason the connection fails, PK232COM will disconnect the link. The format of the entry in the PK232COM.DIR file is as follows. K1HTV ELK v WB4APR-5! SNJ3! NNJ! WMA! SCCT! K1HTV The key word is K1HTV. PK232COM then scans the line to see if there is a '!' in it. If there is it knows that it is dealing with a NET/ROM path. It then tells the TNC to connect to the characters following the key word up to the '!' sign to the TNC in the command mode. In this case it tells the TNC to connect to ELK via WB4APR-5. When the TNC sends back the connected message, PK232COM tells the TNC to try to connect to the next node in the path, namely in this example SNJ3. The sequence continues each time a connection is made until the link is complete. To set up a directory entry just copy the format shown. Place a '!' sign after the uplink path and different node segments. Do not place one after the downlink path. NOTE: All path entries in PK232COM.DIR must be on a single 80 column line. 4.6 CONFIG.SYS You must have a CONFIG.SYS file on the boot disk if you are going to use the disk logging features. This file must contain the line FILES = 20 See the DOS manual for more information about the CONFIG.SYS file. 4.7 *.MBX These are the files associated with the stations you have designated as store and forward mailboxes. Thus if for example you want to use 4Z4ZB as a store and forward mailbox, you will have to create a file called 4Z4ZB.MBX using the non- document mode of your word processor. In this file you will put a list of the call signs of the stations 4Z4ZB can connect to reliably. If for example you want 4Z4ZB to be able to store messages from you to 4X6AA, 4X6LR, G3ZCZ, ON8IK, F0WN,and G8BTB, you would put those call signs in the file, one call on a line as follows. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 46 4X6AA 4X6LR G3ZCZ ON8IK F0WN G8BTB When the QRU function is invoked either by you using Control Function key 3 or by 4Z4ZB connecting to you and sending you the command :QRU: , any messages addressed to any of those stations (EG. G3ZCZ.OUT and ON8IK.OUT) will be transferred from you to 4Z4ZB just as if you had tried to QSP the messages manually or as if G3ZCZ or ON8IK had connected directly to you. The file names will be changed to *.OLD. You must create one file for each designated store and forward station, ie. 4Z4ZB.MBX, G3ZCZ.MBX etc. 4.8 *.BBS These are BBS AUTO-Upload Command files. Each file is named for the callsign of the BBS that you wish to access. It must have exactly the name as the callsign of the BBS. Thus if the BBS is W9TTN-1 the name of the file must be W9TNN-1.BBS, or if the BBS is 4Z4ZB then the file must be called 4Z4ZB.BBS. The file must be an ASCII file. That means the wordprocessor must be used in the non-document mode to create it. This file contains the command sequence that you would have typed at the keyboard if you were accessing the BBS manually. The ONE difference is that the text of a message (you are uploading with the S command must be followed by the character string :EOF: (on a separate line) as illustrated by the example below. The BBS 'S' command (including its variations such as 'SP') is the only multiple line command allowed. You can thus put all the single line commands such as H, ?, L, and R in the command file. A 'multiple command' is defined in this instance as a command which allows you to enter multiple lines before the BBS will send back a '>' character (IE one that the BBS tells you to type in text and terminate it with the Control Z character). The contents of A TYPICAL *.BBS file are shown below as an example. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 47 ----------------------------------------------------------------- k 1234 s g8btb Test Message This is a test message. :EOF: sp ON8IK @ G3ZCZ Greetings The text of this message is greetings from PK232COM. May you register as a user and enjoy it for many years. :EOF: lm r 567 r 593 ----------------------------------------------------------------- NOTE: the 'K 1234' command was used to delete the mail that had already been read. Try not to use 'KM" as you may delete mail BEFORE reading it. The outgoing mail was placed next in the file in case of an abnormal disconnect. The lm command was used to record the message numbers, and to see what old messages were still present on the BBS. Lastly a list of messages to be read was included (the numbers had been recorded in the last BBS_Mail_Snatch). There were also no blank lines in the file. Each message ended with the :EOF: character string, but there was no need for any special end of BBS file character. In the event of a BBS Mail_Snatch, if the *.BBS file exists for that BBS, the file will be processed and the contents sent. Thus if you don't get a chance to send the mail, before the PK232COM download the mail from the BBS, it will send it for you. When the BBS has accepted the commands the name of the file is changed from *.BBS to *.OLD ( IE. the file name KE8X.BBS is changed to KE8X.OLD). In the real world however, message formats are non standard, and can contain any set of characters. The algorithm developed here transmits the next line in the *.BBS file when PK232COM see's a 'trigger' character_string unless one of the 'inhibitor' character_strings is also present on the line of the message text received by PK232COM. These 'trigger' character_strings are '>' (as the last character of the line of text ), 'Enter', 'Subject', 'Sj:' and 'Msg:'. The 'inhibitor' character_strings are 'R:', '<' and 'Message'(R: as in routing headers and < and Message as in Message-Id: <message number> in message headers). This should cover most simulated manual message reading, BBS (WA7MBL and W0RLI/VE3GYQ) forwarding and avoid false triggering due to '>'s showing up in message and routing PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 48 headers. NOTE than when PK232COM finishes processing the *.BBS file, it will send a 'B' command to the BBS to terminate the session. This feature is designed to minimize the time you spend connected to the BBS by allowing you to scan the message list when automatically receiving your mail, prepare your replies and download requests off-line and then later read the incoming messages or files without tying up the BBS. It thus positively disconnects you from the BBS. NOTE: If you upload the 'KM' command from your *.BBS file, you may delete messages before reading them. Do delete 'read' mail from your local BBS. Don't clutter his disk with your read mail. The 'LM' command is built into PK232COM to remind you of what you have out there. 5.0 Initialization 5.1 Copy the files to a working disk. 5.2 Edit PK232COM.SYS. If you are upgrading from a previous version of PK232COM, note that the new .SYS file may not compatible with the old one. 5.3 Copy the new PK232COM.SYS onto the old one. 5.4 Put the working disk into the active drive (the one with the > prompt). 5.5 Make sure that the file CONFIG.SYS exists and contains the statement FILES=20. 5.6 If you are not running a PK-232, strap the DCD in the TNC to follow the connect state. Read the TNC manual to do this. If you do NOT do this, the Conference and bridge modes will NOT work. 6.0 Running the Program 6.1 Make sure that the PK-232 is connected to the computer. 6.2 Make sure that the DOS calendar date and time are set to UTC. 6.3 Run the program by typing the word PK232COM followed by the ENTER key. 6.4 When the program begins, you will default to PACKET mode on VHF (Just like the PK-232 at switch on) in the TRAFFIC terminal mode. If the PK-232 is not set to the correct baud rate and parity type the * characters as explained in the PK-232 manual. 6.5 Initialize the TNC using Alternate Function key 2. If the PK-232 does not have any batteries in it, make sure that the RS-232 link between the TNC and the computer is connected then load and run PK232COM. When the initialization is over, power up the TNC and type a few '*' characters as requested in the manual. Once you see the sign on message, configure the TNC using Alternate function key number 2. To save you going through this rigmarole each time you power up the unit, put some batteries in the TNC. Use good quality PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 49 ones so that they don't leak over the circuit board. 7.0 Mailbox features 7.1 Answering Machine. The program includes an AMTOR (Robot beacon CQ mode only) and PACKET mode SMART "answering machine" facility. You can leave messages on your disk (in the same directory as the PK232COM.* files, if you are using a hard disk), for different stations. When someone connects to you, if you left a message for him, he (or she or even it as the case may be) and only that station will receive it automatically. No one else will normally be able to download that message. 7.2 Mail Beacon (Annunciator). To ensure that people know that you have left a message for them a 'MAIL for' list is loaded into your Packet Beacon and transmitted every 30 minutes (Refer to the BTEXT command in the TNC manual) as ':QTC:' followed by a list of calls. If no mail is pending, or the only message in your system is one addressed to you, the beacon transmissions are inhibited. This conforms to good operating practice on crowded channels (at least inhibiting the beacon does). The mail beacon in the AMTOR mode is transmitted as part of the beacon autocq message. It is automatically updated when a message is transmitted. If you don't set the beacon (see below) you will not transmit a mail beacon text in your AMTOR CQ message. The Mail beacon text is set up either when you tell the computer to set it up using Shift function key 6 or when you disconnect a packet QSO from another station. In this manner you may update the list while the program is running, for example by using Sidekick to write a message, or preferably the NOTE function, and then with a stroke of Shift function key 6, you will update the mail announcement on your beacon. Any station using PK232COM Version 1.42+ can be configured (default state) to automatically attempt a connect (QTC_Snatch) when seeing their callsign in someone else's PK232COM :QTC: beacon mail message list. If for some reason the message got lost (eg. because the link was marginal), :QSM: in version 1.42+ will get you a repeat of that message. 7.3 How to leave a message You can use the note function (Control function key 3) or type the message as a non-document file on Wordstar, or if you use PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 50 another word processor, you must leave the message as an ASCII text file. You may also use the NOTE function built into the program. If you do, the message will be given a header as if it came in from someone else. if you use a word processor to write the message, you will have to write in a header or show somehow that the message is not 'live'. You just name the message file as the callsign of the station to whom you wish the message to be sent at connect time. You must also give it the filetype of 'OUT'. For example a message for G3ZCZ would be stored on the disk as a file named 'G3ZCZ.OUT', and similarly a message to 4X6AA would be stored on disk as '4X6AA.OUT'. You can then use the utility program TIMETAG, to put a message header on message files created by the word processor. In this way people will realize that it is an automatic message by seeing the header. On the other hand, you may wish to fool people into thinking that you are home. Once the message has been sent, an entry to that effect will be made in the PK232COM.RUN data capture file. The message file will then be renamed and given the file extension '.OLD'. At that time any previously existing mail file with the file extension '.OLD' will be deleted. This stops the addressee receiving the message on successive connects if you can't delete it for some reason (you forget) while at the same time, the message is still available to you in case you need it. You should use a utility program if you want the calls in the mail beacon sorted. You may for example wish to sort them alphanumerically or in the order of the date that they were left in your answering machine. Incoming messages triggered by the QTC_Snatch will be left in a message file ( <yourcall.OUT> ), which can be scanned by using the Alternate 'M' function key (PK232COM 1.46+). If you have non PK232COM friends, train them to trigger the QTC_Snatch by simulating a beacon, and prefixing and ending their text with lines containing the '>' as the only character. 7.4 Remote File Downloading (Packet/AMTOR Modes Only). There comes a time when you want to leave a file on your system for someone to download later. You can do this by using NC/L to control the transfer. You must leave the file in a subdirectory called \PK232COM\FILES. You must first create it if it does not exist. The station who wants the message just asks for it using :QBM: <filename>, note they do not need to use the full subdirectory path. They must however leave a single space character between :QBM: and the filename. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 51 In AMTOR the Mailbox must be turned on for remote control functions. For example, you have the latest ARRL DX bulletin, and you want to pass it on. You could pass it to selected people by copying the file to individual messages with the filetype '.OUT', eg. 4X6AA.OUT, 4Z4ZB.OUT or even G3ZCZ.OUT if you want me to get it, which wastes a lot of disk space. On the other hand you could tell people that the file was available for downloading, either in the CTEXT connect message line which everyone gets when connecting to you, or in individual ('.OUT') messages. If you include the following in your CTEXT message "ARRLDX.015 now available" people will know that to download it, they just have to type the line ':QBM: ARRLDX.015' (one space character between :QBM: and the file name) to get the file. PK232COM is not designed as a BBS, however, if you copy the contents of the \PK232COM\FILES subdirectory into a file called DIR (USE DIR > DIR in DOS), anyone can get a list of files the files you have stored in it for downloading by typing :QBM: DIR. Since they do not get the real directory, just what was in it at the time you copied it into the file 'DIR', you may keep "hidden" files in this subdirectory. You may thus leave a file for someone to download, tell them by leaving them a message (which they will get automatically when they connect) and no one else connecting will know that it is there. When the QRU function is invoked either by you using Control Function key 3 or by 4Z4ZB connecting to you and sending you the command :QRU:, any messages addresses to any of those stations (EG. G3ZCZ.OUT and ON8IK.OUT) will be transferred from you to 4Z4ZB just as if you had tried to QSP the messages manually or G3ZCZ or ON8IK had connected to you. The file names will be changed from *.OUT to *.OLD. You may only use the QRU function with stations designated as Store and Forward mailboxes. Put a list of stations that you can connect to reliably in your <callsign>.MBX file and send it to other stations in your LAN also using PK232COM Rev 1.36 or higher. They will then be able to dump their mail messages on you and you on them. If they do the same and send you their file, then you will be able to send messages via them for stations that they can work. While QRU gives you the capability to bulk upload messages to another station in your local area, when you take your machine off line, it may also be used to transfer messages between two LANs (such as the Baltimore and Washington DC Areas) via well sighted gateway digipeaters. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 52 7.5 Remote Beacon shutdown. I recognize that some stations may abuse the beacon facility of this program. I have thus built into the program a 'remote shutdown' capability. If someone running PK232COM has their beacon timer set too often, connect to them in the AMTOR or Packet Communications modes, and tell them to :QRT: which will clear their beacon mode and take them off the air for a while at least. In the Packet communications mode, the CQ beacon is shut down but the 30 minute mail beacon is not touched. In the AMTOR communications mode, the CQ delay time is set to 255. The Mailbox will thus still be active in both modes, but will not beacon on the air at the frequency it was set at. APPENDIX 0. UPDATES/REVISION HISTORY 1.30 PACKET MODE Automatic Logging of Connects. Automatic CQ beacon added. AMTOR Time shown in 'OVER' sequence. Callsign sequence text added in ARQ call. Automatic CQ beacon added with logging in beacon mode. NON PACKET MODES Semi automatic logging added. Call sequence changed to one line except for CQ calls. Retry sequence works in all modes. 1.31 Contest Mode. Function key 3 operation slightly modified. AMTOR answering machine added. Overwrite of status window fixed. 1.32 Packet Mode Store and forward LAN :QSP: capability added. 1.33 :QBM: message/file downloading added in Packet Mode. Digipeat traffic mode logging added. File handle bug. 1.34 File handle bug fixed, logging/capture file opens/closes with each QSO. Digipeat detect works for reciprocal operators, ie >G3ZCZ> for G3ZCZ/4X. Logbook file created if non existent. Some changes in AMTOR beacon signal recognition algorithm. PK232COM.DIR directory added. 1.35 Digipeat detect now stores data as well as address information on disk. 1.36 LAN :QRU: store and forward added, code condensed. Display of Multiple connect mode added. Changes in NC/L :QBM: changed to :QRV: in message mode only. Digipeat logging does not indicate times of logging on/off. 1.37 AMTOR now doesn't send Brag Tape in non beacon automatic CQ mode. Timeout added in PACKET Beacon mode to stop station connecting and holding system. 1.38 V and H (direct Packet mode VHF/HF) added to function key 6. Code condensed again. AMTOR ROBOT override manual mode added. Packet loop back call added. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 53 1.39 CQ text change added to Alt F6. AMTOR non beacon mode auto CQ sends a callsign sequence and +? when someone calls in. Note feature added to Contr. F3. QRU echo's QSP to sending terminal. Printer toggle added. RTTY 'RY' changed back to single line in CQ mode. AMTOR CQ works with EPROM version 4/87. Digipeat Display function now toggled on/off by Alt F key (default is OFF). CQ delay time now adjustable on-line. Minor code changes within the program. 1.40 Thirdparty callsign correct in 'QNO 1' response situation. Alt R key (Message Relay Capability toggle) added. TNC type line added to PK232COM.SYS. TNC2 code added. Additional Baud rates added. Internal code condensed. An active Store and forward Relay status is indicated in connect message '*** PK232COM 1.40' by the 'R' suffix. SIGNAL mode [G] added to function 6. Digipeat display function also now controls 'MDIGI'. 1.41 Packet mode Baudrate, shift reverses (change in 1.40) now done in command mode. Delay added in Alternate function key 2 (TNC Initialize routine). Commands transmitted in command window, replies now show up in INwindow. 1.42 Path determination capability (get other stations 'MH' list), :QMH: added, multi user modes including conferencing, code compaction. Packet mode Alert function added. '/' character added in message header between date and time, Terminal baud rate now 1200/2400/4800/9600, Receive buffer expanded from 128 bytes to 1K bytes. QTC_Snatch added. Packet mode Target call function added. Outgoing text color changed to light green (shows up better on mono CRT used with CGA). Timetag of logged events now includes dates. :QSM: for repeat of messages, AMTOR Robot/Mail Beacon/Mail headers now without ? marks. Digipeat display and logging function (Alternate F key) now works for TNC2. Alt B key, Direct Baudot/ASCII baud rate setup added. Alt F5 or 'MH' now has own window. QTC_Snatch bug in TNC2. 1.43 QTC_Snatch bug fixed. Target call function now also works properly via digipeater. 'DCD on' not sent to non PK-232 TNC's. 1.44 'MH' window module code changed. NET/ROM path added in PK232COM.DIR file. TNC1 capability added. Remote TNC2 disconnect now returns you to command mode. 1.45 TNC specific code modified. PgUp key function added. AMTOR function key 8 now turns off transmitter and puts you in ALIST mode. Mailbox added to AMTOR mode. AMTOR Robot/Mailbox call recognition algorithm improved. Target call changed to Alternate T key. Alt C key now same as Function key 7. MH, Help and DIR windows displays, freeze until key depressed. Input buffer size increased to 8K. Check added on setting of CQ Delay. Dialog condensed to save memory space. QTC_Snatch is LAN-LINK compatible. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 54 1.46 AMTOR mode function key 8 now toggles FEC/ALIST modes. Software selected HF/VHF switching of KPC TNC added. PK-232 transmit buffer now also flushed in non packet modes before a 'call' (Fk 7) sequence. 'CMSG ON' no longer built into start up code, ie. can now be set by operator. QRU (Control Fk 3) works with stations with SSID's. In previous versions it would work only in packet if the MBX file contained the SSID (ie. G3ZCZ-8.MBX instead of G3ZCZ.MBX). Message scan feature (Alt M) added. :QDB: Remote ASCII file upload capability added (Reverse of QBM). BBS_Mail_Snatch added. Alt Fk2 no longer asks you to set the PK-232 communications mode if you are using a packet only TNC. Status display updates if dis- connected in middle of mail upload. Code condensed. 1.47 Video display software rewritten and speeded up. Bridge multi connect mode added. QTC_Snatch now puts snatched message in <yourcall>.out incoming message file instead of PK232COM.RUN. 1.48 Changes in connect status displays in multi connect modes. Alt D key redefined. Conference connect status display changed. Beacon text now updated when message count falls to zero, but beacon is still inhibited. Beacon inhibited if only message is to your own station. APPENDIX 1. ANOMALIES (and BUGS) A1.1 Since the Program has no way to check the command/converse mode status of the TNC, you may see various cmd: and error messages from the TNC when using the function key commands. Ignore them for now. If you get an error message, try using the function key again. A1.2 In the AMTOR Beacon CQ mode, if the other station drops the link while you are recording the text, BEFORE the callsign has been recognized as a valid callsign, PK232COM will time out before logging the QSO and restarting the CQ sequence. If someone else calls in before the timeout has occurred, the text from both stations should be captured to disk, but the log entry may not show both stations, thus the 'LOG' must be compared with the 'RUN' file for QSL purposes. PK232COM in the Beacon/Mailbox mode, normally logs the contact at the end of the line in which it recognized the callsign as a valid callsign. A1.3 In the AMTOR Beacon CQ or Mailbox mode, if another stations sends a +? in the FEC mode, the beacon will attempt to send the PK232COM.TXT file. The PK-232 however is not in the converse mode at that time and will interpret the text of the file as commands. If by some chance, the text corresponds to a valid command the PK-232 will execute it and you may not notice that it did until you begin to wonder why nobody is replying to the beacon. As such I recommend that the first character of each line in the file PK232COM.TXT be a non valid PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 55 command character such as a number or a period (.) or another punctuation sign. A1.4 PK232COM versions 1.00 to 1.39 were written for a PK-232 with an Oct 1986 ROM. There may be differences with later ROMs. Version 1.39 works with the April 1987 ROM. A1.5 If you are using a CGA card with a monochrome monitor, the text you type into the OUTWINDOW will be fainter than the incoming text. This is because it is set to light green. If you are using a Hercules compatible card you will not notice any difference. A1.6 The conference mode has been tested on a PK-232 and a SANYO MBC-675 which has a clock speed of 4.7MHz. If you have problems with intermittent selection of IO channels try slowing down your CPU clock. There is a software delay loop in the program that is used to allow the TNC time to switch IO streams after receipt of the stream change command. This delay is there because PK232COM tests for a connect on each channel before outputting any text, so that it does not send unaddressed packets on non connected IO channels. A1.7 A Packet conference Mode disconnect returns the TNC to the command mode, even if you remain connected to one or more other stations. A1.8 When using the non packet modes the 'long' time the software takes to rewrite the screens for each character means that there is a delay in following the typing. If this bothers you, set EAS OFF for manual operation (from the command mode), but don't forget to turn it on when using the autocq mode. 1.48 has speeded up displays, but still not as they should be. A1.9 Strange Events. If the TNC does not use an interrupt driven serial port you may experience problems when using baud rates greater than 1200. The PK-232 DOES NOT LIKE PK232COM to use RS-232 baud rates faster than 2400, and sometimes not even that. Use 1200 until YOU have tested and ARE SURE that a faster one will work. IF YOU HAVE ANY STRANGE PROBLEMs AND ARE USING an RS-232 TERMINAL BAUD RATE to the TNC WHICH IS GREATER THAN 1200, set the Terminal Baud Rate to 1200 and see if the problem goes away. A1.10 *** DISCONNECTED In the Packet communications mode, when you are connected to someone and the TNC sends this text string to the computer, PK232COM thinks you have been disconnected and resets. This normally only happens when a true disconnect occurs. However, if the text shows up in the middle of a line being sent to PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 56 you, it WILL HAVE THE SAME EFFECT. A1.11 Greek Characters on Incoming Screen. If you see greek characters in the Incoming screen you probably have the wrong parity set in the TNC. first make sure that the RS-232 baud rate is correct. If it is, take the batteries out of it and reset it. If that fails, play with the parity. PK232COM sets the serial port to 8 bits, no parity. As there are many different configurations of IBM PC Compatibles and TNC's, I can't test all of them before releasing a version of the program. If a function does not work on your configuration, after retrying it using 1200 bauds on the RS-232 line between the computer and the TNC (see Section A1.9), inhibit it and let me know about it. It will be made to work in the subsequent release. APPENDIX 2. Local Area Network Capability VHF Packet radio systems can be considered as part of a Local Area Network (LAN) in which messages can be left by one station in the computer belonging to a second station. At HF the same is true, but the area becomes greater. The basic problem here is that people can only send and receive messages to or from you when you are on-line. To compensate for this, BBS stations were developed which allowed both messages and bulletins to be stored by anyone for later retrieval. PK232COM allows you to store messages in your computer so as to use it as an automatic answering machine. Thus by storing the messages in a file called by the name of callsign, with the file extension '.OUT', anyone connecting to the computer will get their message without having to request it. PK232COM Version 1.32 extends that concept to cover the eventuality of you wanting to take your computer off-line for some reason. You may now load the message into any other computer you can connect to using elements of the Q code adapted to the High Level Network Communications Language (NC/L) proposed in my book Software for Amateur Radio, (Book number 1560) published by TAB Books, Blue Ridge Summit, Pa. 17214 USA. A2.1 LAN Protocol (G3ZCZ Version) The protocol is as follows. When connected to someone who has their computer configured as a host, if you want to store a message you send the following instruction to the other station :QSP: <callsign> where <callsign> is the call of the station that the message is for, not the callsign of the host station in whose computer you are storing the message. [Note use only one space character after the :QSP:. PK232COM sends the :QSP: message automatically using Control Function Key 3. For example if you want to store a message for 4Z4ZB in 4X6AA's computer which is configured as a Store and Forward system, you would first connect to 4X6AA and then send the PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 57 message as :QSP: 4Z4ZB . Better still use function key 3 to automate the sequence. The computer at 4X6AA will respond either with a statement saying that it is ready for you to go ahead, or send a message saying that it can't comply. If it is ready you get a positive reply which will take the form :QRV: <callsign> which if you know the Q code, means " I am ready to accept a message for <callsign>". At this time you may go ahead and send the message. If you type the message at the keyboard, you may use either a control Z (^Z) character or the character sequence :EOF: followed by a carriage return (the ENTER key) to terminate the message. If you have first written the message into a text file you may then send it using function key 2 and the termination sequence is automatic. Once you have completed the message, the other (host) computer will either reply that the message has been successfully stored or give you an error message. If the message is stored and ready to be sent next time the addressee connects to that computer, you will see the message :QSL: on your screen. If something went wrong, you will get back a negative message taking the form :QNO: followed by a number. The number tells you why the operation failed. A2.2 Message Format The message is stored just as if you had left it in your system (except that a header is added identifying the time of reception and the call of the sending station). It will contain a header showing the date and time it was received and your callsign. Should a message for that station already be in the system, yours will be appended to it. In the event the your upload is aborted, the amount of text received before the abort occurred will be stored as the message. When you disconnect from the host station, its mail beacon will be updated. Once the message is loaded in the host, it can only be deleted by the operator of the host station. When the addressee connects to the host and receives the message, the file type will change from '.OUT' to '.OLD'. A2.3 File Uploading/Downloading. See section 7.4 for the use of :QBM: for downloading text or ASCII files from another PK232COM system. :QDB: allows you to upload text or ASCII files. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 58 A2.4 Path Determination to a Dx station If you want to establish a digipeat path to a station somewhat out of your direct range, you need to know which of the stations that you can connect to can hear that desired DX station. If you could get a call monitored (MH list) from the stations that you connect to, you would be able to see if the station you are connected to has heard your desired DX station. PK232COM uses the :QMH: command to request such a list. When PK232COM (Version 1.42+) receives a :QMH: command, it drops back to the TNC command mode and issues a 'MH' command to the TNC (except to a TNC1 which does not support it). It stores the list received in a temporary buffer, and then returns to the converse mode and transmits the list back to the station it is linked to. By judicious use of :QMH: you can determine paths to other stations. Note however, that just because one station can hear another station, it does not mean that it can work it. For example, the station you are connected to (running PK232COM Version 1.42 or greater) may be using a power level of 1 watt or so, while the station 200 miles away that it heard was using 100 watts. Test the path yourself, or/and leave a message asking how reliable the connect path between those two stations is. If you and a small group use a non standard packet channel for intergroup communications, you may also use the :QMH: function to find out who the station you are connected with, has heard recently, when you first sign on the LAN channel. APPENDIX 3 BASIC NC/L DICTIONARY Messages can be transferred into any other PK232COM computer you can connect with using elements of the Q code adapted to the High Level Network Communications Language (NC/L) proposed in my book Software for Amateur Radio, (Book number 1560) published by TAB Books, Blue Ridge Summit, Pa. 17214 USA. To receive a message, do nothing, you will receive your mail auto- matically when connecting/linking with a PK232COM station. You cannot normally read messages addressed to another person. A3.1 :QBM: To download a file, send :QBM: filename.type The filename.type is the file you want. For example :QBM: dir :QBM: help :QBM: pk232com.doc PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 59 A3.2 :QDB: To upload files to another PK232COM (1.46+) system send :QDB: filename.type Files will be uploaded into the same sub-directory as PK232COM, and will have a message header inserted at the top of the file to allow the operator to know who uploaded the file. If the operator then wants to make the file available for downloading, he or she can move it to the \PK232COM\FILES sub-directory. The '.TYP' following the filename is optional. If you attempt to upload a file which has the same name as one that already exists on the remote system, you will receive a :QNO: 14 'error' message. This command is the reverse of :QBM:. A3.3 :QMH: To request a call monitored list ('MH') from the station that you are connected with using PK232COM (1.42+), send :QMH: A3.4 :QSM: To request a repeat of a message from a station using PK232COM (1.42+), send :QSM:. This command will be valid as long as the host station has not deleted the <yourcall>.OLD file on his disk. If the file does not exist, you will receive a :QNO: 2 'error' response. A3.5 :QSP: To leave a message, send :QSP: callsign the callsign is that of the station you wish to leave a message for. A3.6 :QRT: To shut down an AMTOR/Packet mode Mailbox/beacon station which is causing QRM, link or connect to the station and send :QRT: A3.7 :QRU: To upload messages from one PK232COM (1.38+) system to your computer, send :QRU: Computer responses A3.8 :QNO: 'NO' or error QNO Error Values. The following error numbers are associated with message store and forward operations. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 60 ? What you typed was not an NC/L command. 1 Computer not configured as Store and Forward system. 2 Requested ASCII file/ message (:QBM:) does not exist. 3 You made an error in the name of the callsign for whom the message is intended (It must be at least 3 characters long). 4 File creation error in host system. 5 Error occurred during reception and storage of message. Could be that the computer ran out of space on the disk, or something else went wrong in storing the message. 6 :QRU: You are not authorized as a store and forward mailbox. 7 :QRU: Error in opening <callsign>.MBX file. 8 :QRU: Error in closing <callsign>.MBX file. 9 :QRU: Sequence Error in callsign of message to go. The bad callsign will be shown after the error number. 14 :QDB: File Name In Use Error. The name you gave the file you want to upload already exists on that system. Try a different name. 90 NC/L defined function not implemented in this release. 99 PK232COM compatible program, but requested function has not been implemented. A3.9 :QJG: The QRU sequence is complete. There are no more messages pending. A3.10 :QRV: callsign The computer is ready you to send the message. End the message with a control Z (^Z) character, or the sequence :EOF: . A3.11 :QSL: callsign Confirms receipt of message to that callsign or that a file has been successfully uploaded and stored to disk. It is also used to acknowledge receipt of a ':QRT:' command. A3.12 :QTC: messsage list. This precedes a list of callsigns for whom messages are stored up on a computer. It is used in Packet Beacon transmissions or AMTOR Beacon mode CQ calls. If PK232COM receives :QTC: it will respond with the beacon text showing the mail queue. You can configure your version of PK232COM to issue a QTC_Snatch connect request to any other station using the PK232COM beacon transmission to signal that you have a message waiting. NOTE: If you are not using a TNC1 you MUST set the PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 61 TNC HEADERLN parameter to ON. The packet headers and the text of the packets must show up on your screen on separate lines. PROPOSED EXTENSIONS A3.13 :QYU: YAPP format file upload. A3.14 :QYD: YAPP format file download. APPENDIX 4. USING OTHER TNC'S. PK232COM was first written for the PK-232. However it has since been modified so that the PACKET mode capabilities can be used on other TNC's. There are minor differences in the command dialog between different TNC's. The dialog differences affecting the operation of PK232COM are built into the program and set when the TNC type is read from the PK232COM.SYS file at the program load time. The non packet modes will obviously result in error messages if attempted on a packet mode TNC. The following notes apply to different TNC's or digital communications controllers. A4.1 TNC2 (MFJ 1270) A4.1.1 Default Commands. Delete or rename the PK232COM.SYS file. Rename the TNC2.SYS file to PK232COM.SYS and edit it using your wordprocessor in its non document mode to customize it to your station.Add in the default state for the TNC commands not included in the file and make sure that you set AUTOLF ON and MCON ON. If you are going to use the conference mode, set the multi user defaults to show the callsign in the text header that the TNC sends to the computer. A4.1.2 Program differences. The following functions DO NOT WORK because the TNC does not support them. All NON PACKET modes. Software controlled HF/VHF switching. Software controlled baudrate switching. MAIL Packet terminal mode (Alternate Function key 4). CQ/BEACON Packet terminal mode (Alternate Function key 4). TNC Transmit Buffer flush (Control Function key 9). A4.2 TNC1 (HD-4040) A4.2.1 Default Commands. Delete or rename the PK232COM.SYS file. Rename the TNC1.SYS file to PK232COM.SYS and edit it using your wordprocessor in PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 62 its non document mode to customize it to your station. A4.2.2 Program differences. The following functions DO NOT WORK because the TNC does not support them. All NON PACKET modes. Day/Time functions (Control function key 1). 'MH' and remote :QMH: functions (Alternate Function key 5). MAIL Packet terminal mode (Alternate Function key 4). CQ/BEACON Packet terminal mode (Alternate Function key 4). TNC Transmit Buffer flush (Control Function key 9). Conference and multi-connect modes. A4.3 Kaypro KPC-2 A4.3.1 Default Commands. Set all parameters as if you have a TNC2. Edit the PK232COM.SYS file as if you have a TNC2. Then add a line to set CCITT OFF. A4.3.2 Program differences. The following functions DO NOT WORK because the TNC does not support them. All NON PACKET modes. MAIL Packet terminal mode (Alternate Function key 4). CQ/BEACON Packet terminal mode (Alternate Function key 4). TNC Transmit Buffer flush (Control Function key 9). APPENDIX 5. NOTES and ACKNOWLEDGEMENTS I'd like to acknowledge the contributions to PK232COM by the following persons, in alphanumeric order. 4X1AA Milt: Without Milt's initial encouragement, PK232COM Version 1.00 would never have been written. 4X4GI Yair: who first loaned me a TNC2 manual. K1HTV Rich: who suggested the 'PgUp backscroll' feature. K8DD Hank: who suggested the Conference mode. K8PNW Tom: who suggested the 'Target Call' feature. KD8SL Paul: who loaned me a TNC1. KL7VZ George: who helped with the AMTOR beacon/mailbox tests. W9TNN George: who let me play with his KPC-2 and manual. WB8COX Tom: whose modifications of the Public Domain Turbo Pascal MODEM software (by Jack Wierda and Steve Freeman used in versions 1.00 to 1.44) were further modified and incorporated in PK232COM Versions 1.45 to 1.48. WB8WKA Jeff: who suggested the Alt S key to turn the sound off. PK232COM.DOC (c) G3ZCZ 1988 PK232COM VERSION 1.48 PAGE 63 I'm always interested in your bug reports, comments and suggestions for changes. In particular, what if any, binary file transfer mode(s) should be supported. For the latest information on Updates, read the UPDATE.* files on the distribution disk. APPENDIX 6 PK232COM REGISTRATION FORM. To: Joe Kasser G3ZCZ P O BOX 3419 SILVER SPRING MD 20904. CALL ________________ TODAY'S DATE _____________ NAME ______________________________________________ ADDRESS ___________________________________________ ___________________________________________ CITY ___________________________________________ STATE _________ POST CODE ______________________ TNC TYPE _____________________ I enclose a check for $35.00. Please send me the latest version of PK232COM customized to my call and TNC, and register me as a user of PK232COM. I am currently using Version ___________ which I obtained from _________________________________________. The first 12 lines of my current PK232COM.SYS file are listed in the blank space below. Signature Comments, likes, dislikes, wish list, etc. PK232COM.DOC (c) G3ZCZ 1988